BAYARD

GLEIF verified
LEI
9695009RO1TBYQDF0S61
Registered name
BAYARD
Jurisdiction
Ultimate parent
No parent on file in GLEIF
Cluster stats
Netblocks7
Registered in France (5) · Russia (2)
All fragments 8 blocks across 2 clusters
Cluster ID208820523
RegistryRIPE
Owner jurisdictionFR
Customersfind customers using this network →
Evidence & provenance ?
Attribution GLEIF legal-entity match
Legal identityLEI 9695009RO1TBYQDF0S61
Shared handles clustered on 6 shared RIR contact/maintainer handles
Registry names 3 distinct registrant names across these blocks
full provenance (JSON) → · how attribution works

Footprint over time

5 weekly snapshots · JSON
7 0 netblocks since 2026-07-05
2026-07-05 peak 7 2026-07-19

IP Ranges (7)

⬇ export CSV
CIDR Org name Registry Status Confidence
62.244.121.192/30 BAYARD-NET RIPE ASSIGNED PA ● low
212.248.67.32/30 Bayard RIPE ASSIGNED PA ● low
213.147.44.144/29 BAYARD RIPE ASSIGNED PA ● low
213.244.25.128/30 BAYARD RIPE ASSIGNED PA ● low
213.244.25.132/30 BAYARD RIPE ASSIGNED PA ● low
213.244.25.136/29 BAYARD RIPE ASSIGNED PA ● low
217.112.234.88/29 BAYARD RIPE ASSIGNED PA ● low

Possibly related to this organisation

what's this?
Same name family
Separately-registered clusters whose names share “BAYARD” — often per-country or per-system registrations of the same brand, occasionally a different organisation sharing the name. Not counted in this organisation's own footprint.
Sub-allocations under carriers
IP blocks an ISP reassigned to a similarly-named customer — decoded from the ISP's own naming convention, not a direct registration.

Network trust

what's this?
RPKI hygiene: B how networks compare →
85.7% of checked blocks have valid RPKI ROA coverage (6 of 7)
No discrepancies found among checked blocks.

NIC Handles

BLUEGIX-MNT COMPLETEL-MNT DUMY-RIPE DUMY-RIPE FMCF-MNT MTU-NOC