bgpreport

Network · data from 2026-11-12

AS17082 SMART-CITY-MBCC - SMART CITY NETWORKS, LIMITED PARTNERSHIP

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

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS17082, 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.
23.92.202.0/24 No ROA Nonecovered by 23.92.200.0/22 671 100% 69
23.92.200.0/24 No ROA Nonecovered by 23.92.200.0/22 667 99% 68
23.92.201.0/24 No ROA Nonecovered by 23.92.200.0/22 667 99% 68
23.92.203.0/24 No ROA Nonecovered by 23.92.200.0/22 667 99% 68
24.56.139.0/24 No ROA RIR databaseARIN, RADB 667 99% 68
208.115.78.0/23 No ROA RIR databaseARIN, RADB 667 99% 68
23.92.200.0/22 No ROA RIR databaseARIN, RADB 2 0%low visibility 2

AS-SET

AS17082 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 12 are in fix.csv.

  • ROA: none7
  • Route object: none4
  • Route object: not announced1
ChangePrefix or setDetailFull-table peers
ROA: none23.92.202.0/24No ROA covers it. Add a ROA for AS17082, maxLength 24.671 of 673
Route object: none23.92.202.0/24No route object for it. A route object for 23.92.200.0/22 with origin AS17082 covers it (filters allowing more-specifics accept it). Add a route object with origin AS17082 in the RIR database for the space.671 of 673
ROA: none23.92.200.0/24No ROA covers it. Add a ROA for AS17082, maxLength 24.667 of 673
Route object: none23.92.200.0/24No route object for it. A route object for 23.92.200.0/22 with origin AS17082 covers it (filters allowing more-specifics accept it). Add a route object with origin AS17082 in the RIR database for the space.667 of 673
ROA: none23.92.201.0/24No ROA covers it. Add a ROA for AS17082, maxLength 24.667 of 673
Route object: none23.92.201.0/24No route object for it. A route object for 23.92.200.0/22 with origin AS17082 covers it (filters allowing more-specifics accept it). Add a route object with origin AS17082 in the RIR database for the space.667 of 673
ROA: none23.92.203.0/24No ROA covers it. Add a ROA for AS17082, maxLength 24.667 of 673
Route object: none23.92.203.0/24No route object for it. A route object for 23.92.200.0/22 with origin AS17082 covers it (filters allowing more-specifics accept it). Add a route object with origin AS17082 in the RIR database for the space.667 of 673
ROA: none24.56.139.0/24No ROA covers it. Add a ROA for AS17082, maxLength 24.667 of 673
ROA: none208.115.78.0/23No ROA covers it. Add a ROA for AS17082, maxLength 23.667 of 673
ROA: none23.92.200.0/22No ROA covers it. Add a ROA for AS17082, maxLength 22.2 of 673

Route objects not announced

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

2604:b180:470::/44RADBNo 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.