bgpreport

Network · data from 2026-11-12

AS395415 QT-SEC - Quiktrip Corporation

Registry name: QT-SEC - Quiktrip Corporation, US · not in PeeringDB

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

Announced routes

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

8.42.249.0/24 No ROA None 673 100% 67
148.78.84.0/23 No ROA Nonecovered by 148.78.84.0/22 673 100% 67
148.78.84.0/24 No ROA Nonecovered by 148.78.84.0/22 673 100% 67
148.78.85.0/24 No ROA Nonecovered by 148.78.84.0/22 673 100% 67
148.78.86.0/23 No ROA Nonecovered by 148.78.84.0/22 673 100% 67
148.78.87.0/24 No ROA Other IRR onlyRADB 671 100% 69
148.78.86.0/24 No ROA Other IRR onlyRADB 670 100% 68

AS-SET

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

  • ROA: none7
  • Route object: none5
  • Route object: RIR2
  • Route object: not announced1
ChangePrefix or setDetailFull-table peers
ROA: none8.42.249.0/24No ROA covers it. Add a ROA for AS395415, maxLength 24.673 of 673
Route object: none8.42.249.0/24No route object for it. Add a route object with origin AS395415 in the RIR database for the space.673 of 673
ROA: none148.78.84.0/23No ROA covers it. Add a ROA for AS395415, maxLength 23.673 of 673
Route object: none148.78.84.0/23No route object for it. A route object for 148.78.84.0/22 with origin AS395415 covers it (filters allowing more-specifics accept it). Add a route object with origin AS395415 in the RIR database for the space.673 of 673
ROA: none148.78.84.0/24No ROA covers it. Add a ROA for AS395415, maxLength 24.673 of 673
Route object: none148.78.84.0/24No route object for it. A route object for 148.78.84.0/22 with origin AS395415 covers it (filters allowing more-specifics accept it). Add a route object with origin AS395415 in the RIR database for the space.673 of 673
ROA: none148.78.85.0/24No ROA covers it. Add a ROA for AS395415, maxLength 24.673 of 673
Route object: none148.78.85.0/24No route object for it. A route object for 148.78.84.0/22 with origin AS395415 covers it (filters allowing more-specifics accept it). Add a route object with origin AS395415 in the RIR database for the space.673 of 673
ROA: none148.78.86.0/23No ROA covers it. Add a ROA for AS395415, maxLength 23.673 of 673
Route object: none148.78.86.0/23No route object for it. A route object for 148.78.84.0/22 with origin AS395415 covers it (filters allowing more-specifics accept it). Add a route object with origin AS395415 in the RIR database for the space.673 of 673
ROA: none148.78.87.0/24No ROA covers it. Add a ROA for AS395415, maxLength 24.671 of 673
Route object: RIR148.78.87.0/24Route object only in RADB. Add it in the RIR database for the space.671 of 673
ROA: none148.78.86.0/24No ROA covers it. Add a ROA for AS395415, maxLength 24.670 of 673
Route object: RIR148.78.86.0/24Route object only in RADB. Add it in the RIR database for the space.670 of 673

Route objects not announced

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

148.78.84.0/22RADBNo 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.