bgpreport

Network · data from 2026-11-12

AS22827 SMART-CITY-OCCC - SMART CITY NETWORKS, LIMITED PARTNERSHIP

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

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS22827, 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.
208.115.70.0/23 No ROA None 670 100% 67
207.190.32.0/21 No ROA RIR databaseARIN 672 100% 67
24.54.156.0/22 No ROA RIR databaseARIN 670 100% 67
24.56.129.0/24 No ROA RIR databaseARIN 670 100% 67
24.56.130.0/24 No ROA RIR databaseARIN 670 100% 67
207.190.40.0/22 No ROA RIR databaseARIN 670 100% 67
207.190.44.0/24 No ROA RIR databaseARIN 670 100% 67
207.190.45.0/24 No ROA RIR databaseARIN 670 100% 67
207.190.46.0/23 No ROA RIR databaseARIN 670 100% 67
208.115.68.0/24 No ROA RIR databaseARIN 670 100% 67
208.115.69.0/24 No ROA RIR databaseARIN 670 100% 67

AS-SET

AS22827 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 14 are in fix.csv.

  • ROA: none11
  • Route object: none1
  • Route object: not announced2
ChangePrefix or setDetailFull-table peers
ROA: none208.115.70.0/23No ROA covers it. Add a ROA for AS22827, maxLength 23.670 of 673
Route object: none208.115.70.0/23No route object for it. Add a route object with origin AS22827 in the RIR database for the space.670 of 673
ROA: none207.190.32.0/21No ROA covers it. Add a ROA for AS22827, maxLength 21.672 of 673
ROA: none24.54.156.0/22No ROA covers it. Add a ROA for AS22827, maxLength 22.670 of 673
ROA: none24.56.129.0/24No ROA covers it. Add a ROA for AS22827, maxLength 24.670 of 673
ROA: none24.56.130.0/24No ROA covers it. Add a ROA for AS22827, maxLength 24.670 of 673
ROA: none207.190.40.0/22No ROA covers it. Add a ROA for AS22827, maxLength 22.670 of 673
ROA: none207.190.44.0/24No ROA covers it. Add a ROA for AS22827, maxLength 24.670 of 673
ROA: none207.190.45.0/24No ROA covers it. Add a ROA for AS22827, maxLength 24.670 of 673
ROA: none207.190.46.0/23No ROA covers it. Add a ROA for AS22827, maxLength 23.670 of 673
ROA: none208.115.68.0/24No ROA covers it. Add a ROA for AS22827, maxLength 24.670 of 673
ROA: none208.115.69.0/24No ROA covers it. Add a ROA for AS22827, maxLength 24.670 of 673

Route objects not announced

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

208.115.70.0/24ARINNo ROA
208.115.71.0/24ARINNo ROA

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.