bgpreport

Network · data from 2026-11-12

AS14556 PTC - Pilot Travel Centers, LLC

Registry name: PTC - Pilot Travel Centers, LLC, US · not in PeeringDB

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

Announced routes

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

70.159.149.0/24 No ROA None 672 100% 67
65.196.143.0/24 No ROA RIR databaseARIN 672 100% 67
74.114.190.0/24 Valid None 672 100% 67
74.114.188.0/24 Valid None 671 100% 67
74.114.189.0/24 Valid None 671 100% 67

AS-SET

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

  • ROA: none2
  • Route object: none4
ChangePrefix or setDetailFull-table peers
ROA: none70.159.149.0/24No ROA covers it. Add a ROA for AS14556, maxLength 24.672 of 673
Route object: none70.159.149.0/24No route object for it. Add a route object with origin AS14556 in the RIR database for the space.672 of 673
ROA: none65.196.143.0/24No ROA covers it. Add a ROA for AS14556, maxLength 24.672 of 673
Route object: none74.114.190.0/24No route object for it. Add a route object with origin AS14556 in the RIR database for the space.672 of 673
Route object: none74.114.188.0/24No route object for it. Add a route object with origin AS14556 in the RIR database for the space.671 of 673
Route object: none74.114.189.0/24No route object for it. Add a route object with origin AS14556 in the RIR database for the space.671 of 673

Route objects not announced

Every route object with origin AS14556 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.