bgpreport

Network · data from 2026-11-12

AS64227 CONSOLIDATED TELEPHONE AS 64227

Registry name: CTC-AS2 - CONSOLIDATED TELEPHONE COMPANY, US · PeeringDB

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

Announced routes

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

142.202.52.0/22 No ROA RIR databaseARIN 671 100% 68
192.234.192.0/23 No ROA RIR databaseARIN 671 100% 68
50.20.196.0/22 Valid RIR databaseARIN 671 100% 68
64.237.104.0/22 Valid RIR databaseALTDB, ARIN 671 100% 68
134.49.244.0/22 Valid RIR databaseARIN 671 100% 68
148.64.62.0/23 Valid RIR databaseALTDB, ARIN 671 100% 68
2606:df80::/32 Valid RIR databaseARIN 635 100% 69

AS-SET

PeeringDB's irr_as_set for AS64227: AS-CTC-TRANSIT. 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 (AS64227 isn't in the set, or no route object for AS64227 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 objectsAS64227 in itNot covered
AS-CTC-TRANSIT ARIN 16181 Yes 0

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

  • ROA: none2
  • Route object: not announced1
ChangePrefix or setDetailFull-table peers
ROA: none142.202.52.0/22No ROA covers it. Add a ROA for AS64227, maxLength 22.671 of 673
ROA: none192.234.192.0/23No ROA covers it. Add a ROA for AS64227, maxLength 23.671 of 673

Route objects not announced

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

2606:4f40::/32ARINNo 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.