bgpreport

Network · data from 2026-11-12

AS208439 Fiberon-ISP-AS Fiberon LLC

Registry name: Fiberon-ISP-AS Fiberon LLC, AZ · not in PeeringDB

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

Announced routes

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

45.136.164.0/22 Valid None 673 100% 66

AS-SET

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

  • Route object: none1
  • Route object: not announced13
ChangePrefix or setDetailFull-table peers
Route object: none45.136.164.0/22No route object for it. Add a route object with origin AS208439 in the RIR database for the space.673 of 673

Route objects not announced

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

45.136.164.0/25RIPEInvalid: maxLength
45.136.164.128/27RIPEInvalid: maxLength
45.136.164.160/27RIPEInvalid: maxLength
45.136.164.192/27RIPEInvalid: maxLength
45.136.164.224/27RIPEInvalid: maxLength
45.136.165.0/24RIPEInvalid: maxLength
45.136.166.0/24RIPEValid
45.136.167.0/25RIPEInvalid: maxLength
45.136.167.128/27RIPEInvalid: maxLength
45.136.167.160/27RIPEInvalid: maxLength
45.136.167.192/27RIPEInvalid: maxLength
45.136.167.224/27RIPEInvalid: maxLength
2a0e:9ec0::/29RIPEValid

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.