bgpreport

Network · data from 2026-11-12

AS397285 CAMBRIDGETELEPHONECO - Cambridge Telephone

Registry name: CAMBRIDGETELEPHONECO - Cambridge Telephone, US · not in PeeringDB

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

Announced routes

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

45.33.208.0/22 Valid RIR databaseARIN 671 100% 67
45.33.212.0/22 Valid RIR databaseARIN 671 100% 67
45.33.216.0/24 Valid RIR databaseARIN 670 100% 67
45.33.220.0/24 Valid RIR databaseARIN 670 100% 67
45.33.223.0/24 Valid RIR databaseARIN 670 100% 67

AS-SET

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

  • Route object: not announced22

Route objects not announced

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

23.172.192.0/24ARINValid
45.33.208.0/20ARINNo ROA
45.33.217.0/24ARINValid
45.33.218.0/24ARINValid
45.33.219.0/24ARINValid
45.33.221.0/24ARINValid
45.33.222.0/24ARINValid
66.232.72.0/21ARINNo ROA
66.232.80.0/22ARINNo ROA
199.58.120.0/21ARINNo ROA
199.58.120.0/24ARINValid
199.58.121.0/24ARINValid
199.58.122.0/24ARINValid
199.58.123.0/24ARINValid
199.58.124.0/24ARINValid
199.58.125.0/24ARINValid
199.58.126.0/24ARINValid
199.58.127.0/24ARINValid
208.98.170.0/24ARINNo ROA
208.98.176.0/22ARINNo ROA
209.19.132.0/23ARINInvalid: origin
2606:6580::/32ARINValid

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.