bgpreport

Network · data from 2026-11-12

AS15313 PMTL-AS1 - Pembroke Telephone Company, Inc.

Registry name: PMTL-AS1 - Pembroke Telephone Company, Inc., US · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS15313, 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.
74.124.144.0/24 No ROA Nonecovered by 74.124.144.0/20 668 99% 67
74.124.144.0/20 No ROA Other IRR onlyRADB 669 99% 67
206.180.224.0/20 No ROA Other IRR onlyRADB 669 99% 67
74.124.156.0/24 No ROA Other IRR onlyRADB 668 99% 67
74.124.157.0/24 No ROA Other IRR onlyRADB 668 99% 67
74.124.159.0/24 No ROA Other IRR onlyRADB 668 99% 67
147.124.232.0/23 Valid None 668 99% 67
147.124.232.0/24 Valid None 668 99% 67
147.124.233.0/24 Valid None 668 99% 67
147.124.236.0/23 Valid None 668 99% 67
147.124.236.0/24 Valid None 668 99% 67
147.124.237.0/24 Valid None 668 99% 67
150.252.192.0/21 Valid Other IRR onlyRADB 668 99% 67

AS-SET

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

  • ROA: none6
  • Route object: none7
  • Route object: RIR6
ChangePrefix or setDetailFull-table peers
ROA: none74.124.144.0/24No ROA covers it. Add a ROA for AS15313, maxLength 24.668 of 673
Route object: none74.124.144.0/24No route object for it. A route object for 74.124.144.0/20 with origin AS15313 covers it (filters allowing more-specifics accept it). Add a route object with origin AS15313 in the RIR database for the space.668 of 673
ROA: none74.124.144.0/20No ROA covers it. Add a ROA for AS15313, maxLength 20.669 of 673
Route object: RIR74.124.144.0/20Route object only in RADB. Add it in the RIR database for the space.669 of 673
ROA: none206.180.224.0/20No ROA covers it. Add a ROA for AS15313, maxLength 20.669 of 673
Route object: RIR206.180.224.0/20Route object only in RADB. Add it in the RIR database for the space.669 of 673
ROA: none74.124.156.0/24No ROA covers it. Add a ROA for AS15313, maxLength 24.668 of 673
Route object: RIR74.124.156.0/24Route object only in RADB. Add it in the RIR database for the space.668 of 673
ROA: none74.124.157.0/24No ROA covers it. Add a ROA for AS15313, maxLength 24.668 of 673
Route object: RIR74.124.157.0/24Route object only in RADB. Add it in the RIR database for the space.668 of 673
ROA: none74.124.159.0/24No ROA covers it. Add a ROA for AS15313, maxLength 24.668 of 673
Route object: RIR74.124.159.0/24Route object only in RADB. Add it in the RIR database for the space.668 of 673
Route object: none147.124.232.0/23No route object for it. Add a route object with origin AS15313 in the RIR database for the space.668 of 673
Route object: none147.124.232.0/24No route object for it. Add a route object with origin AS15313 in the RIR database for the space.668 of 673
Route object: none147.124.233.0/24No route object for it. Add a route object with origin AS15313 in the RIR database for the space.668 of 673
Route object: none147.124.236.0/23No route object for it. Add a route object with origin AS15313 in the RIR database for the space.668 of 673
Route object: none147.124.236.0/24No route object for it. Add a route object with origin AS15313 in the RIR database for the space.668 of 673
Route object: none147.124.237.0/24No route object for it. Add a route object with origin AS15313 in the RIR database for the space.668 of 673
Route object: RIR150.252.192.0/21Route object only in RADB. Add it in the RIR database for the space.668 of 673

Route objects not announced

Every route object with origin AS15313 is announced.

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.