bgpreport

Network · data from 2026-11-12

AS399515 PEERTAG-INFRA-CORE - PeerTag LLC

Registry name: PEERTAG-INFRA-CORE - PeerTag LLC, US · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS399515, 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.
5.175.204.0/24 Invalid: origin Other origin only 2 0%low visibility 2
151.240.244.0/22 No ROA Other origin only 2 0%low visibility 2
94.74.171.0/24 Valid RIR databaseRIPE 673 100% 67
102.177.146.0/23 Valid RIR databaseAFRINIC 672 100% 67

AS-SET

AS399515 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 5 are in fix.csv.

  • ROA: origin1
  • ROA: none1
  • Route object: none2
  • Route object: not announced1
ChangePrefix or setDetailFull-table peers
ROA: origin5.175.204.0/24ROAs covering it name AS12586, not AS399515. If AS399515 should announce it, add a ROA for AS399515.2 of 673
Route object: none5.175.204.0/24Route objects for it name AS12586. Add a route object with origin AS399515 in the RIR database for the space.2 of 673
ROA: none151.240.244.0/22No ROA covers it. Add a ROA for AS399515, maxLength 22.2 of 673
Route object: none151.240.244.0/22Route objects for it name AS20473. Add a route object with origin AS399515 in the RIR database for the space.2 of 673

Route objects not announced

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

130.78.24.0/24RIPEValid

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.