bgpreport

Network · data from 2026-11-12

AS23277 SMART-CITY-SDCC - SMART CITY NETWORKS, LIMITED PARTNERSHIP

Registry name: SMART-CITY-SDCC - SMART CITY NETWORKS, LIMITED PARTNERSHIP, US · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS23277, 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.
2604:b180:250::/44 No ROA Other IRR onlyRADB 3 0%low visibility 3
66.78.208.0/21 No ROA RIR databaseARIN, RADB 673 100% 67
96.8.48.0/20 No ROA RIR databaseARIN, RADB 673 100% 67
208.115.72.0/23 No ROA RIR databaseARIN, RADB 673 100% 67

AS-SET

AS23277 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 5 are in fix.csv.

  • ROA: none4
  • Route object: RIR1
ChangePrefix or setDetailFull-table peers
ROA: none2604:b180:250::/44No ROA covers it. Add a ROA for AS23277, maxLength 44.3 of 636
Route object: RIR2604:b180:250::/44Route object only in RADB. Add it in the RIR database for the space.3 of 636
ROA: none66.78.208.0/21No ROA covers it. Add a ROA for AS23277, maxLength 21.673 of 673
ROA: none96.8.48.0/20No ROA covers it. Add a ROA for AS23277, maxLength 20.673 of 673
ROA: none208.115.72.0/23No ROA covers it. Add a ROA for AS23277, maxLength 23.673 of 673

Route objects not announced

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