bgpreport

Network · data from 2026-11-12

AS13868 Peak Internet

Registry name: PEAK INTERNET - Peak Internet, US · PeeringDB

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

Announced routes

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

199.26.172.0/24 No ROA None 673 100% 67
206.125.64.0/19 No ROA RIR databaseARIN 673 100% 67
207.55.0.0/17 No ROA RIR databaseARIN 673 100% 67
69.59.192.0/19 No ROA RIR databaseARIN 670 100% 67
2607:f678::/32 No ROA RIR databaseARIN 631 99% 68
208.80.84.0/22 Valid RIR databaseARIN 672 100% 67

AS-SET

PeeringDB's irr_as_set for AS13868: AS-PEAKINTERNET. Expanded from the day's IRR dumps the way bgpq4 does against whois.radb.net: a name with a database is read from that database only, one without from the first database in RADB's order. "Not covered" = this network's own routes that a filter built from the set would leave out (AS13868 isn't in the set, or no route object for AS13868 covers the route; more-specifics of a route object are accepted down to /24 and /48, as with bgpq4 -A -R 24 / -R 48). Customers' routes aren't counted: the collectors show each route's origin, not which network it came through.

NameDatabaseASNsSets Route objectsAS13868 in itNot covered
AS-PEAKINTERNET ARIN 141109 Yes 1

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: none5
  • Route object: none1
ChangePrefix or setDetailFull-table peers
ROA: none199.26.172.0/24No ROA covers it. Add a ROA for AS13868, maxLength 24.673 of 673
Route object: none199.26.172.0/24No route object for it. Add a route object with origin AS13868 in the RIR database for the space.673 of 673
ROA: none206.125.64.0/19No ROA covers it. Add a ROA for AS13868, maxLength 19.673 of 673
ROA: none207.55.0.0/17No ROA covers it. Add a ROA for AS13868, maxLength 17.673 of 673
ROA: none69.59.192.0/19No ROA covers it. Add a ROA for AS13868, maxLength 19.670 of 673
ROA: none2607:f678::/32No ROA covers it. Add a ROA for AS13868, maxLength 32.631 of 636

Route objects not announced

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