bgpreport

Network · data from 2026-11-12

AS36316 SHOREHAMTEL - GoNetSpeed

Registry name: SHOREHAMTEL - GoNetSpeed, US · not in PeeringDB

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

Announced routes

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

2607:4a00::/36 No ROA Nonecovered by 2607:4a00::/32 636 100% 67
67.217.124.0/22 No ROA Other IRR onlyALTDB, RADB 670 100% 68
199.101.176.0/22 Valid RIR databaseALTDB, ARIN, RADB 670 100% 68
208.65.160.0/21 Valid RIR databaseARIN 670 100% 68

AS-SET

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

  • ROA: none2
  • Route object: none1
  • Route object: RIR1
  • Route object: not announced3
ChangePrefix or setDetailFull-table peers
ROA: none2607:4a00::/36No ROA covers it. Add a ROA for AS36316, maxLength 36.636 of 636
Route object: none2607:4a00::/36No route object for it. A route object for 2607:4a00::/32 with origin AS36316 covers it (filters allowing more-specifics accept it). Add a route object with origin AS36316 in the RIR database for the space.636 of 636
ROA: none67.217.124.0/22No ROA covers it. Add a ROA for AS36316, maxLength 22.670 of 673
Route object: RIR67.217.124.0/22Route object only in ALTDB, RADB. Add it in the RIR database for the space.670 of 673

Route objects not announced

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

173.214.64.0/21ARINValid
2607:4a00::/32ALTDBNo ROA
2607:4a00:6000::/35ARINValid

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.