bgpreport

Network · data from 2026-11-12

AS25636 ONTL-2002 - NorthernTel Limited Partnership

Registry name: ONTL-2002 - NorthernTel Limited Partnership, CA · not in PeeringDB

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

Announced routes

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

64.25.160.0/19 No ROA Other origin only 673 100% 67
76.8.112.0/20 No ROA Other origin only 673 100% 67
173.255.24.0/21 No ROA Other origin only 673 100% 67
209.105.192.0/19 No ROA Other origin only 673 100% 67
206.108.252.0/23 No ROA None 671 100% 67
206.108.254.0/24 No ROA Other origin only 671 100% 67

AS-SET

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

  • ROA: none6
  • Route object: none6
  • Route object: not announced1
ChangePrefix or setDetailFull-table peers
ROA: none64.25.160.0/19No ROA covers it. Add a ROA for AS25636, maxLength 19.673 of 673
Route object: none64.25.160.0/19Route objects for it name AS19752. Add a route object with origin AS25636 in the RIR database for the space.673 of 673
ROA: none76.8.112.0/20No ROA covers it. Add a ROA for AS25636, maxLength 20.673 of 673
Route object: none76.8.112.0/20Route objects for it name AS19752. Add a route object with origin AS25636 in the RIR database for the space.673 of 673
ROA: none173.255.24.0/21No ROA covers it. Add a ROA for AS25636, maxLength 21.673 of 673
Route object: none173.255.24.0/21Route objects for it name AS11666. Add a route object with origin AS25636 in the RIR database for the space.673 of 673
ROA: none209.105.192.0/19No ROA covers it. Add a ROA for AS25636, maxLength 19.673 of 673
Route object: none209.105.192.0/19Route objects for it name AS19752. Add a route object with origin AS25636 in the RIR database for the space.673 of 673
ROA: none206.108.252.0/23No ROA covers it. Add a ROA for AS25636, maxLength 23.671 of 673
Route object: none206.108.252.0/23No route object for it. Add a route object with origin AS25636 in the RIR database for the space.671 of 673
ROA: none206.108.254.0/24No ROA covers it. Add a ROA for AS25636, maxLength 24.671 of 673
Route object: none206.108.254.0/24Route objects for it name AS19752. Add a route object with origin AS25636 in the RIR database for the space.671 of 673

Route objects not announced

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

199.71.128.0/21RADBNo 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.