bgpreport

Network · data from 2026-11-12

AS394352 Fastnet Communications

Registry name: FLEXNETWORKS-MDU - FlexNetworks, CA · PeeringDB

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

Announced routes

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

2602:fe57::/36 No ROA Other IRR onlyRADB 635 100% 69
104.224.32.0/23 Valid RIR databaseARIN, RADB 671 100% 68
104.224.32.0/24 Valid RIR databaseARIN 671 100% 68
104.224.33.0/24 Valid RIR databaseARIN 671 100% 68
104.224.35.0/24 Valid RIR databaseARIN 671 100% 68
161.129.245.0/24 Valid RIR databaseARIN 671 100% 68
23.166.32.0/24 Valid RIR databaseARIN 670 100% 68
64.234.118.0/24 Valid RIR databaseARIN 670 100% 68
104.224.34.0/24 Valid RIR databaseARIN 670 100% 68
158.51.244.0/24 Valid RIR databaseARIN 670 100% 68
158.51.245.0/24 Valid RIR databaseARIN 670 100% 68
158.51.246.0/24 Valid RIR databaseARIN 670 100% 68
158.51.247.0/24 Valid RIR databaseARIN 670 100% 68
161.38.14.0/24 Valid RIR databaseARIN 670 100% 68
192.219.0.0/24 Valid RIR databaseARIN 670 100% 68

AS-SET

AS394352's PeeringDB record names no 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 8 are in fix.csv.

  • ROA: none1
  • Route object: RIR1
  • Route object: not announced6
ChangePrefix or setDetailFull-table peers
ROA: none2602:fe57::/36No ROA covers it. Add a ROA for AS394352, maxLength 36.635 of 636
Route object: RIR2602:fe57::/36Route object only in RADB. Add it in the RIR database for the space.635 of 636

Route objects not announced

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

104.224.32.0/22ARINValid
104.224.34.0/23ARIN, RADBValid
158.51.244.0/22ARINValid
158.51.244.0/23ARINValid
158.51.246.0/23ARINValid
2001:470:2a3::/48ARINValid

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.