bgpreport

Network · data from 2026-11-12

AS207134 PHOENIXNAP-SRB PHOENIX NAP, LLC.

Registry name: PHOENIXNAP-SRB PHOENIX NAP, LLC., US · not in PeeringDB

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

Announced routes

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

131.153.98.0/24 Valid None 671 100% 66
2a00:8860:500::/40 Valid None 605 95% 67
131.153.40.0/23 Valid Other IRR onlyRIPE-NONAUTH 671 100% 66
131.153.96.0/23 Valid Other IRR onlyRIPE-NONAUTH 671 100% 66

AS-SET

AS207134 isn't in PeeringDB, where networks name their 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 4 are in fix.csv.

  • Route object: none2
  • Route object: RIR2
ChangePrefix or setDetailFull-table peers
Route object: none131.153.98.0/24No route object for it. Add a route object with origin AS207134 in the RIR database for the space.671 of 673
Route object: none2a00:8860:500::/40No route object for it. Add a route object with origin AS207134 in the RIR database for the space.605 of 636
Route object: RIR131.153.40.0/23Route object only in RIPE-NONAUTH. Add it in the RIR database for the space.671 of 673
Route object: RIR131.153.96.0/23Route object only in RIPE-NONAUTH. Add it in the RIR database for the space.671 of 673

Route objects not announced

Every route object with origin AS207134 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.