bgpreport

Network · data from 2026-11-12

AS209360 Bulud Telecom

Registry name: bulud Bulud Telecom LLC, AZ · PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS209360, 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.

213.154.24.0/22 Invalid: origin None 1 0%low visibility 1
130.193.74.0/24 No ROA RIR databaseRIPE 673 100% 66
2a0d:2700::/29 No ROA RIR databaseRIPE 635 100% 68
154.61.82.0/24 Valid RIR databaseARIN 673 100% 66
193.105.123.0/24 Valid RIR databaseRIPE 673 100% 66
38.27.37.0/24 Valid RIR databaseARIN 672 100% 66

AS-SET

AS209360'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.

  • ROA: origin1
  • ROA: none2
  • Route object: none1
  • Route object: not announced2
ChangePrefix or setDetailFull-table peers
ROA: origin213.154.24.0/22ROAs covering it name AS28787, not AS209360. If AS209360 should announce it, add a ROA for AS209360.1 of 673
Route object: none213.154.24.0/22No route object for it. Add a route object with origin AS209360 in the RIR database for the space.1 of 673
ROA: none130.193.74.0/24No ROA covers it. Add a ROA for AS209360, maxLength 24.673 of 673
ROA: none2a0d:2700::/29No ROA covers it. Add a ROA for AS209360, maxLength 29.635 of 636

Route objects not announced

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

37.61.77.0/24RIPEInvalid: origin
37.61.78.0/24RIPEInvalid: origin

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.