bgpreport

Network · data from 2026-11-12

AS18731 CITYSIDE-01 - Cityside Fiber

Registry name: CITYSIDE-01 - Cityside Fiber, US · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS18731, 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.
154.50.58.0/24 No ROA RIR databaseARIN 673 100% 67
128.177.138.0/24 Valid None 673 100% 67
157.238.80.0/20 Valid None 673 100% 67
198.170.224.0/19 Valid None 673 100% 67
2607:73c0::/33 Valid Nonecovered by 2607:73c0::/32 636 100% 67
2607:73c0:8000::/33 Valid Nonecovered by 2607:73c0::/32 636 100% 67
23.164.40.0/24 Valid RIR databaseARIN 673 100% 67
2607:73c0::/32 Valid RIR databaseARIN 635 100% 67

AS-SET

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

  • ROA: none1
  • Route object: none5
ChangePrefix or setDetailFull-table peers
ROA: none154.50.58.0/24No ROA covers it. Add a ROA for AS18731, maxLength 24.673 of 673
Route object: none128.177.138.0/24No route object for it. Add a route object with origin AS18731 in the RIR database for the space.673 of 673
Route object: none157.238.80.0/20No route object for it. Add a route object with origin AS18731 in the RIR database for the space.673 of 673
Route object: none198.170.224.0/19No route object for it. Add a route object with origin AS18731 in the RIR database for the space.673 of 673
Route object: none2607:73c0::/33No route object for it. A route object for 2607:73c0::/32 with origin AS18731 covers it (filters allowing more-specifics accept it). Add a route object with origin AS18731 in the RIR database for the space.636 of 636
Route object: none2607:73c0:8000::/33No route object for it. A route object for 2607:73c0::/32 with origin AS18731 covers it (filters allowing more-specifics accept it). Add a route object with origin AS18731 in the RIR database for the space.636 of 636

Route objects not announced

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