bgpreport

Network · data from 2026-11-12

AS55218 IWISP-LLC - iWiSP llc

Registry name: IWISP-LLC - iWiSP llc, US · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS55218, 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:fd3d:592::/48 No ROA Nonecovered by 2602:fd3d:400::/38 635 100% 67
2602:fd3d:593::/48 No ROA Nonecovered by 2602:fd3d:400::/38 635 100% 67
2602:fd3d:60::/48 No ROA Nonecovered by 2602:fd3d::/38 634 100% 67
2602:fd3d:61::/48 No ROA Nonecovered by 2602:fd3d::/38 633 100% 67
139.64.141.0/24 No ROA Other IRR onlyRADB 668 99% 67
139.64.140.0/24 No ROA RIR databaseARIN, RADB 673 100% 67
139.64.143.0/24 No ROA RIR databaseARIN, RADB 671 100% 68
2602:fd3d::/36 No ROA RIR databaseARIN, RADB 634 100% 67

AS-SET

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

  • ROA: none8
  • Route object: none4
  • Route object: RIR1
  • Route object: not announced12
ChangePrefix or setDetailFull-table peers
ROA: none2602:fd3d:592::/48No ROA covers it. Add a ROA for AS55218, maxLength 48.635 of 636
Route object: none2602:fd3d:592::/48No route object for it. A route object for 2602:fd3d:400::/38 with origin AS55218 covers it (filters allowing more-specifics accept it). Add a route object with origin AS55218 in the RIR database for the space.635 of 636
ROA: none2602:fd3d:593::/48No ROA covers it. Add a ROA for AS55218, maxLength 48.635 of 636
Route object: none2602:fd3d:593::/48No route object for it. A route object for 2602:fd3d:400::/38 with origin AS55218 covers it (filters allowing more-specifics accept it). Add a route object with origin AS55218 in the RIR database for the space.635 of 636
ROA: none2602:fd3d:60::/48No ROA covers it. Add a ROA for AS55218, maxLength 48.634 of 636
Route object: none2602:fd3d:60::/48No route object for it. A route object for 2602:fd3d::/38 with origin AS55218 covers it (filters allowing more-specifics accept it). Add a route object with origin AS55218 in the RIR database for the space.634 of 636
ROA: none2602:fd3d:61::/48No ROA covers it. Add a ROA for AS55218, maxLength 48.633 of 636
Route object: none2602:fd3d:61::/48No route object for it. A route object for 2602:fd3d::/38 with origin AS55218 covers it (filters allowing more-specifics accept it). Add a route object with origin AS55218 in the RIR database for the space.633 of 636
ROA: none139.64.141.0/24No ROA covers it. Add a ROA for AS55218, maxLength 24.668 of 673
Route object: RIR139.64.141.0/24Route object only in RADB. Add it in the RIR database for the space.668 of 673
ROA: none139.64.140.0/24No ROA covers it. Add a ROA for AS55218, maxLength 24.673 of 673
ROA: none139.64.143.0/24No ROA covers it. Add a ROA for AS55218, maxLength 24.671 of 673
ROA: none2602:fd3d::/36No ROA covers it. Add a ROA for AS55218, maxLength 36.634 of 636

Route objects not announced

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

63.117.64.0/24RADBNo ROA
139.64.140.0/22ARIN, RADBNo ROA
139.64.142.0/24RADBNo ROA
169.128.64.0/22ARIN, RADBNo ROA
169.128.64.0/23RADBNo ROA
169.128.64.0/24ARIN, RADBNo ROA
169.128.65.0/24ARIN, RADBNo ROA
169.128.66.0/23RADBNo ROA
169.128.66.0/24RADBNo ROA
169.128.67.0/24RADBNo ROA
2602:fd3d::/38ARINNo ROA
2602:fd3d:400::/38ARINNo ROA

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.