bgpreport

Network · data from 2026-11-12

AS11272 C Spire Fiber

Registry name: TELEPAK-NETWORKS-INC - C Spire Fiber, US · PeeringDB

36IPv4 routes 66.7% RPKI valid · 55.6% with a route object
1IPv6 routes 100.0% RPKI valid · 100.0% with a route object
1RPKI invalid 1 origin · 0 maxLength
11No ROA 16 with no route object for this origin
7Low visibility seen by under 10% of full-table peers
13Route objects not announced registered with origin AS11272, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS11272, 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.

69.197.192.0/18 Invalid: origin Other origin only 13 2%low visibility 14
162.210.119.0/24 No ROA Other origin only 672 100% 67
172.99.218.0/23 No ROA Other origin only 672 100% 67
74.113.94.0/24 No ROA Other origin only 671 100% 67
8.42.176.0/20 No ROA Other IRR onlyALTDB 672 100% 67
38.140.64.0/19 No ROA Other IRR onlyALTDB 672 100% 67
198.160.253.0/24 No ROA Other IRR onlyALTDB 672 100% 67
204.128.222.0/24 No ROA Other IRR onlyALTDB 672 100% 67
64.28.48.0/20 No ROA RIR databaseARIN 672 100% 67
69.57.48.0/20 No ROA RIR databaseARIN 672 100% 67
207.179.32.0/19 No ROA RIR databaseARIN 672 100% 67
207.179.38.0/24 No ROA RIR databaseARIN 672 100% 67
50.86.252.0/24 Valid Nonecovered by 50.86.0.0/16 672 100% 67
66.175.136.0/24 Valid Nonecovered by 66.175.128.0/18 672 100% 67
167.160.217.0/24 Valid Nonecovered by 167.160.192.0/19 672 100% 67
167.160.219.0/24 Valid Nonecovered by 167.160.192.0/19 672 100% 67
173.235.46.0/24 Valid Nonecovered by 173.235.0.0/16 672 100% 67
173.235.108.0/24 Valid Nonecovered by 173.235.0.0/16 672 100% 67
50.86.62.0/24 Valid Nonecovered by 50.86.0.0/16 2 0%low visibility 2
66.175.135.0/24 Valid Nonecovered by 66.175.128.0/18 2 0%low visibility 2
167.160.210.0/24 Valid Nonecovered by 167.160.192.0/19 2 0%low visibility 2
167.160.211.0/24 Valid Nonecovered by 167.160.192.0/19 2 0%low visibility 2
199.33.90.0/24 Valid Nonecovered by 199.33.90.0/23 2 0%low visibility 2
199.33.91.0/24 Valid Nonecovered by 199.33.90.0/23 2 0%low visibility 2
66.175.128.0/18 Valid RIR databaseARIN 672 100% 67
67.20.0.0/20 Valid RIR databaseARIN 672 100% 67
69.89.208.0/20 Valid RIR databaseARIN 672 100% 67
76.8.224.0/19 Valid RIR databaseARIN 672 100% 67
104.232.160.0/19 Valid RIR databaseARIN 672 100% 67
136.239.0.0/17 Valid RIR databaseARIN 672 100% 67
167.160.192.0/19 Valid RIR databaseARIN 672 100% 67
198.28.144.0/20 Valid RIR databaseARIN 672 100% 67
198.28.160.0/19 Valid RIR databaseARIN 672 100% 67
199.33.90.0/23 Valid RIR databaseARIN 672 100% 67
50.86.0.0/16 Valid RIR databaseARIN 669 99% 67
173.235.0.0/16 Valid RIR databaseARIN 669 99% 67
2607:f4a0::/32 Valid RIR databaseARIN 635 100% 68

AS-SET

PeeringDB's irr_as_set for AS11272: ARIN::AS-TELEPAK-C. Expanded from the day's IRR dumps the way bgpq4 does against whois.radb.net: a name with a database is read from that database only, one without from the first database in RADB's order. "Not covered" = this network's own routes that a filter built from the set would leave out (AS11272 isn't in the set, or no route object for AS11272 covers the route; more-specifics of a route object are accepted down to /24 and /48, as with bgpq4 -A -R 24 / -R 48). Customers' routes aren't counted: the collectors show each route's origin, not which network it came through.

NameDatabaseASNsSets Route objectsAS11272 in itNot covered
ARIN::AS-TELEPAK-C ARIN4 member sets in no database: AS-HARBORCOM-C, AS-TECINFO, AS10700:AS-CONE, AS19684:AS-CONE 11261,452 Yes 4

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

  • ROA: origin1
  • ROA: none11
  • Route object: none16
  • Route object: RIR4
  • AS-SET: missing member4
  • Route object: not announced13
ChangePrefix or setDetailFull-table peers
ROA: origin69.197.192.0/18ROAs covering it name AS15212, not AS11272. If AS11272 should announce it, add a ROA for AS11272.13 of 673
Route object: none69.197.192.0/18Route objects for it name AS15212. Add a route object with origin AS11272 in the RIR database for the space.13 of 673
ROA: none162.210.119.0/24No ROA covers it. Add a ROA for AS11272, maxLength 24.672 of 673
Route object: none162.210.119.0/24Route objects for it name AS18896. Add a route object with origin AS11272 in the RIR database for the space.672 of 673
ROA: none172.99.218.0/23No ROA covers it. Add a ROA for AS11272, maxLength 23.672 of 673
Route object: none172.99.218.0/23Route objects for it name AS398907. Add a route object with origin AS11272 in the RIR database for the space.672 of 673
ROA: none74.113.94.0/24No ROA covers it. Add a ROA for AS11272, maxLength 24.671 of 673
Route object: none74.113.94.0/24Route objects for it name AS18896, AS32592. Add a route object with origin AS11272 in the RIR database for the space.671 of 673
ROA: none8.42.176.0/20No ROA covers it. Add a ROA for AS11272, maxLength 20.672 of 673
Route object: RIR8.42.176.0/20Route object only in ALTDB. Add it in the RIR database for the space.672 of 673
ROA: none38.140.64.0/19No ROA covers it. Add a ROA for AS11272, maxLength 19.672 of 673
Route object: RIR38.140.64.0/19Route object only in ALTDB. Add it in the RIR database for the space.672 of 673
ROA: none198.160.253.0/24No ROA covers it. Add a ROA for AS11272, maxLength 24.672 of 673
Route object: RIR198.160.253.0/24Route object only in ALTDB. Add it in the RIR database for the space.672 of 673
ROA: none204.128.222.0/24No ROA covers it. Add a ROA for AS11272, maxLength 24.672 of 673
Route object: RIR204.128.222.0/24Route object only in ALTDB. Add it in the RIR database for the space.672 of 673
ROA: none64.28.48.0/20No ROA covers it. Add a ROA for AS11272, maxLength 20.672 of 673
ROA: none69.57.48.0/20No ROA covers it. Add a ROA for AS11272, maxLength 20.672 of 673
ROA: none207.179.32.0/19No ROA covers it. Add a ROA for AS11272, maxLength 19.672 of 673
ROA: none207.179.38.0/24No ROA covers it. Add a ROA for AS11272, maxLength 24.672 of 673
Route object: none50.86.252.0/24No route object for it. A route object for 50.86.0.0/16 with origin AS11272 covers it (filters allowing more-specifics accept it). Add a route object with origin AS11272 in the RIR database for the space.672 of 673
Route object: none66.175.136.0/24No route object for it. A route object for 66.175.128.0/18 with origin AS11272 covers it (filters allowing more-specifics accept it). Add a route object with origin AS11272 in the RIR database for the space.672 of 673
Route object: none167.160.217.0/24No route object for it. A route object for 167.160.192.0/19 with origin AS11272 covers it (filters allowing more-specifics accept it). Add a route object with origin AS11272 in the RIR database for the space.672 of 673
Route object: none167.160.219.0/24No route object for it. A route object for 167.160.192.0/19 with origin AS11272 covers it (filters allowing more-specifics accept it). Add a route object with origin AS11272 in the RIR database for the space.672 of 673
Route object: none173.235.46.0/24No route object for it. A route object for 173.235.0.0/16 with origin AS11272 covers it (filters allowing more-specifics accept it). Add a route object with origin AS11272 in the RIR database for the space.672 of 673
Route object: none173.235.108.0/24No route object for it. A route object for 173.235.0.0/16 with origin AS11272 covers it (filters allowing more-specifics accept it). Add a route object with origin AS11272 in the RIR database for the space.672 of 673
Route object: none50.86.62.0/24No route object for it. A route object for 50.86.0.0/16 with origin AS11272 covers it (filters allowing more-specifics accept it). Add a route object with origin AS11272 in the RIR database for the space.2 of 673
Route object: none66.175.135.0/24No route object for it. A route object for 66.175.128.0/18 with origin AS11272 covers it (filters allowing more-specifics accept it). Add a route object with origin AS11272 in the RIR database for the space.2 of 673
Route object: none167.160.210.0/24No route object for it. A route object for 167.160.192.0/19 with origin AS11272 covers it (filters allowing more-specifics accept it). Add a route object with origin AS11272 in the RIR database for the space.2 of 673
Route object: none167.160.211.0/24No route object for it. A route object for 167.160.192.0/19 with origin AS11272 covers it (filters allowing more-specifics accept it). Add a route object with origin AS11272 in the RIR database for the space.2 of 673
Route object: none199.33.90.0/24No route object for it. A route object for 199.33.90.0/23 with origin AS11272 covers it (filters allowing more-specifics accept it). Add a route object with origin AS11272 in the RIR database for the space.2 of 673
Route object: none199.33.91.0/24No route object for it. A route object for 199.33.90.0/23 with origin AS11272 covers it (filters allowing more-specifics accept it). Add a route object with origin AS11272 in the RIR database for the space.2 of 673
AS-SET: missing memberARIN::AS-TELEPAK-CAS-TELEPAK-C (ARIN) lists AS-HARBORCOM-C; no IRR database read has it.
AS-SET: missing memberARIN::AS-TELEPAK-CAS-TELEPAK-C (ARIN) lists AS-TECINFO; no IRR database read has it.
AS-SET: missing memberARIN::AS-TELEPAK-CAS-TELEPAK-C (ARIN) lists AS10700:AS-CONE; no IRR database read has it.
AS-SET: missing memberARIN::AS-TELEPAK-CAS-TELEPAK-C (ARIN) lists AS19684:AS-CONE; no IRR database read has it.

Route objects not announced

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

8.42.184.0/21ARINNo ROA
38.140.66.0/24ALTDBNo ROA
38.140.76.0/23ALTDBNo ROA
38.140.82.0/24ALTDBNo ROA
50.86.48.0/21NTTCOMValid
76.8.233.0/24NTTCOMValid
76.8.234.0/24NTTCOMValid
76.8.235.0/24NTTCOMValid
76.8.249.0/24NTTCOMValid
97.75.240.0/24ARINNo ROA
173.235.20.0/24NTTCOMValid
206.130.52.0/24ALTDBNo ROA
207.181.32.0/19ALTDBNo 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.