bgpreport

Network · data from 2026-11-12

AS210743 Babbar SAS

Registry name: BABBAR-AS BABBAR SAS, FR · PeeringDB

4IPv4 routes 100.0% RPKI valid · 100.0% with a route object
2IPv6 routes 100.0% RPKI valid · 50.0% with a route object
0RPKI invalid 0 origin · 0 maxLength
0No ROA 1 with no route object for this origin
1Low visibility seen by under 10% of full-table peers
0Route objects not announced registered with origin AS210743, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS210743, things to look at first. Visibility = full-table peers that see it, of 673 (IPv4) and 636 (IPv6) on 75 collectors. Also as routes.csv.

2001:978:1b04::/48 Valid Nonecovered by 2001:978:1b04::/47 605 95% 67
217.113.194.0/24 Valid RIR databaseRIPE 673 100% 67
2001:978:1b04::/47 Valid RIR databaseRIPE 633 100% 67
217.113.196.0/24 Valid RIR databaseRIPE 72 11% 37
217.113.199.0/24 Valid RIR databaseRIPE 71 11% 36
154.54.249.0/24 Valid RIR databaseARIN, RADB 22 3%low visibility 16

AS-SET

AS210743's PeeringDB record names no AS-SET.

Fix list

The changes that would bring RPKI, the IRR and what's announced into line. Some are deliberate (a route object kept for a backup route, say); the network decides. All 1 are in fix.csv.

  • Route object: none1
ChangePrefix or setDetailFull-table peers
Route object: none2001:978:1b04::/48No route object for it. A route object for 2001:978:1b04::/47 with origin AS210743 covers it (filters allowing more-specifics accept it). Add a route object with origin AS210743 in the RIR database for the space.605 of 636

Route objects not announced

Every route object with origin AS210743 is announced.

Routes: the 08:00 UTC snapshots of 2026-11-12 from 75 RIPE RIS and RouteViews collectors. RPKI: our rpki-client run before the snapshot. IRR: the day's dumps of the five RIR databases and RADB's mirrors. The LEVEL3 and IDNIC databases publish no dump and aren't read, so route objects only there count as none.