bgpreport

Network · data from 2026-11-12

AS13819 FWIN-NET - INDIGITAL TELECOM

Registry name: FWIN-NET - INDIGITAL TELECOM, US · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS13819, 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.
66.249.224.0/20 Valid Nonecovered by 66.249.224.0/19 673 100% 67
66.170.40.0/24 Valid Nonecovered by 66.170.32.0/19 672 100% 67
66.170.50.0/24 Valid Nonecovered by 66.170.32.0/19 672 100% 67
66.170.51.0/24 Valid Nonecovered by 66.170.32.0/19 672 100% 67
66.170.53.0/24 Valid Nonecovered by 66.170.32.0/19 672 100% 67
66.170.60.0/24 Valid Nonecovered by 66.170.32.0/19 672 100% 67
66.170.32.0/19 Valid RIR databaseARIN 673 100% 67
66.249.240.0/20 Valid RIR databaseARIN 673 100% 67
2001:4928::/32 Valid RIR databaseARIN 605 95% 67

AS-SET

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

  • Route object: none6
  • Route object: not announced2
ChangePrefix or setDetailFull-table peers
Route object: none66.249.224.0/20No route object for it. A route object for 66.249.224.0/19 with origin AS13819 covers it (filters allowing more-specifics accept it). Add a route object with origin AS13819 in the RIR database for the space.673 of 673
Route object: none66.170.40.0/24No route object for it. A route object for 66.170.32.0/19 with origin AS13819 covers it (filters allowing more-specifics accept it). Add a route object with origin AS13819 in the RIR database for the space.672 of 673
Route object: none66.170.50.0/24No route object for it. A route object for 66.170.32.0/19 with origin AS13819 covers it (filters allowing more-specifics accept it). Add a route object with origin AS13819 in the RIR database for the space.672 of 673
Route object: none66.170.51.0/24No route object for it. A route object for 66.170.32.0/19 with origin AS13819 covers it (filters allowing more-specifics accept it). Add a route object with origin AS13819 in the RIR database for the space.672 of 673
Route object: none66.170.53.0/24No route object for it. A route object for 66.170.32.0/19 with origin AS13819 covers it (filters allowing more-specifics accept it). Add a route object with origin AS13819 in the RIR database for the space.672 of 673
Route object: none66.170.60.0/24No route object for it. A route object for 66.170.32.0/19 with origin AS13819 covers it (filters allowing more-specifics accept it). Add a route object with origin AS13819 in the RIR database for the space.672 of 673

Route objects not announced

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

66.170.224.0/19RADBNo ROA
66.249.224.0/19ARINValid

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.