bgpreport

Network · data from 2026-11-12

AS204106 Babilon-Mobile

Registry name: Babilon-Mobile CJSC Babilon-Mobile, TJ · PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS204106, 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.
2a13:1b00:1000::/48 Valid Nonecovered by 2a13:1b00::/29 635 100% 70
2a13:1b01:ff00::/48 Valid Nonecovered by 2a13:1b00::/29 634 100% 69
2a13:1b00::/32 Valid Nonecovered by 2a13:1b00::/29 2 0%low visibility 2
2a13:1b01:a00::/48 Valid Nonecovered by 2a13:1b00::/29 2 0%low visibility 2
46.20.202.0/23 Valid RIR databaseRIPE 673 100% 66
46.20.202.0/24 Valid RIR databaseRIPE 673 100% 66
46.20.203.0/24 Valid RIR databaseRIPE 673 100% 66
77.247.198.0/24 Valid RIR databaseRIPE 671 100% 68
109.74.72.0/24 Valid RIR databaseRIPE 671 100% 66
2a13:1b00:4000::/48 Valid RIR databaseRIPE 635 100% 70

AS-SET

AS204106'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 6 are in fix.csv.

  • Route object: none4
  • Route object: not announced2
ChangePrefix or setDetailFull-table peers
Route object: none2a13:1b00:1000::/48No route object for it. A route object for 2a13:1b00::/29 with origin AS204106 covers it (filters allowing more-specifics accept it). Add a route object with origin AS204106 in the RIR database for the space.635 of 636
Route object: none2a13:1b01:ff00::/48No route object for it. A route object for 2a13:1b00::/29 with origin AS204106 covers it (filters allowing more-specifics accept it). Add a route object with origin AS204106 in the RIR database for the space.634 of 636
Route object: none2a13:1b00::/32No route object for it. A route object for 2a13:1b00::/29 with origin AS204106 covers it (filters allowing more-specifics accept it). Add a route object with origin AS204106 in the RIR database for the space.2 of 636
Route object: none2a13:1b01:a00::/48No route object for it. A route object for 2a13:1b00::/29 with origin AS204106 covers it (filters allowing more-specifics accept it). Add a route object with origin AS204106 in the RIR database for the space.2 of 636

Route objects not announced

Route objects with origin AS204106 whose prefix no peer sees AS204106 announce. Many are kept on purpose (backup routes, space announced only in some places).

2a13:1b00::/29RIPEValid
2a13:1b00:1::/48RIPEInvalid: maxLength

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.