bgpreport

Network · data from 2026-11-12

AS15212 C-SPIRE-WIRELESS - C Spire

Registry name: C-SPIRE-WIRELESS - C Spire, US · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS15212, 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.
207.179.40.0/21 No ROA None 672 100% 67
66.175.172.0/24 Valid Nonecovered by 66.175.172.0/22 672 100% 67
66.175.174.0/24 Valid Nonecovered by 66.175.172.0/22 672 100% 67
66.175.175.0/24 Valid Nonecovered by 66.175.172.0/22 672 100% 67
50.86.64.0/21 Valid RIR databaseARIN 672 100% 67
66.175.176.0/24 Valid RIR databaseARIN 672 100% 67
66.175.179.0/24 Valid RIR databaseARIN 672 100% 67
66.175.180.0/23 Valid RIR databaseARIN 672 100% 67
66.175.182.0/24 Valid RIR databaseARIN 672 100% 67
69.197.192.0/21 Valid RIR databaseARIN 672 100% 67
69.197.200.0/21 Valid RIR databaseARIN 672 100% 67
69.197.208.0/21 Valid RIR databaseARIN 672 100% 67
69.197.216.0/21 Valid RIR databaseARIN 672 100% 67
69.197.224.0/21 Valid RIR databaseARIN 672 100% 67
69.197.232.0/21 Valid RIR databaseARIN 672 100% 67
69.197.240.0/21 Valid RIR databaseARIN 672 100% 67
69.197.248.0/21 Valid RIR databaseARIN 672 100% 67
207.179.32.0/23 Valid RIR databaseARIN 672 100% 67
207.179.34.0/23 Valid RIR databaseARIN 672 100% 67
207.179.36.0/23 Valid RIR databaseARIN 672 100% 67
207.179.48.0/20 Valid RIR databaseARIN 672 100% 67
207.179.54.0/24 Valid RIR databaseARIN 672 100% 67
207.179.56.0/21 Valid RIR databaseARIN 672 100% 67
50.86.84.64/27 Valid RIR databaseARIN 1 0%low visibility 1
50.86.84.128/27 Valid RIR databaseARIN 1 0%low visibility 1

AS-SET

AS15212 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 8 are in fix.csv.

  • ROA: none1
  • Route object: none4
  • Route object: not announced3
ChangePrefix or setDetailFull-table peers
ROA: none207.179.40.0/21No ROA covers it. Add a ROA for AS15212, maxLength 21.672 of 673
Route object: none207.179.40.0/21No route object for it. Add a route object with origin AS15212 in the RIR database for the space.672 of 673
Route object: none66.175.172.0/24No route object for it. A route object for 66.175.172.0/22 with origin AS15212 covers it (filters allowing more-specifics accept it). Add a route object with origin AS15212 in the RIR database for the space.672 of 673
Route object: none66.175.174.0/24No route object for it. A route object for 66.175.172.0/22 with origin AS15212 covers it (filters allowing more-specifics accept it). Add a route object with origin AS15212 in the RIR database for the space.672 of 673
Route object: none66.175.175.0/24No route object for it. A route object for 66.175.172.0/22 with origin AS15212 covers it (filters allowing more-specifics accept it). Add a route object with origin AS15212 in the RIR database for the space.672 of 673

Route objects not announced

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

66.175.144.0/24ARINValid
66.175.172.0/22ARINValid
69.197.192.0/18ARINValid

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.