bgpreport

Network · data from 2026-11-12

AS402279 WAWO-GEOSCRY-08 - Geoscry Network LLC

Registry name: WAWO-GEOSCRY-08 - Geoscry Network LLC, US · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS402279, 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.
101.193.228.0/22 No ROA Other origin only 661 98% 67
101.193.232.0/22 No ROA Other origin only 661 98% 67
101.193.236.0/22 No ROA Other origin only 661 98% 67
101.193.240.0/22 No ROA Other origin only 661 98% 67
101.193.244.0/22 No ROA Other origin only 661 98% 67
101.193.248.0/22 No ROA Other origin only 661 98% 67
208.66.228.0/23 No ROA None 2 0%low visibility 2
2.27.132.0/23 Valid RIR databaseRADB, RIPE 673 100% 67
2.27.109.0/24 Valid RIR databaseRADB, RIPE 671 100% 67
213.110.70.0/23 Valid RIR databaseRADB, RIPE 671 100% 67
2602:f486:fd::/48 Valid RIR databaseARIN 635 100% 67

AS-SET

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

  • ROA: none7
  • Route object: none7
  • Route object: not announced15
ChangePrefix or setDetailFull-table peers
ROA: none101.193.228.0/22No ROA covers it. Add a ROA for AS402279, maxLength 22.661 of 673
Route object: none101.193.228.0/22Route objects for it name AS53587, AS62573, AS135091. Add a route object with origin AS402279 in the RIR database for the space.661 of 673
ROA: none101.193.232.0/22No ROA covers it. Add a ROA for AS402279, maxLength 22.661 of 673
Route object: none101.193.232.0/22Route objects for it name AS53587, AS62573, AS135091. Add a route object with origin AS402279 in the RIR database for the space.661 of 673
ROA: none101.193.236.0/22No ROA covers it. Add a ROA for AS402279, maxLength 22.661 of 673
Route object: none101.193.236.0/22Route objects for it name AS53587, AS62573, AS135091. Add a route object with origin AS402279 in the RIR database for the space.661 of 673
ROA: none101.193.240.0/22No ROA covers it. Add a ROA for AS402279, maxLength 22.661 of 673
Route object: none101.193.240.0/22Route objects for it name AS53587, AS62573, AS135091. Add a route object with origin AS402279 in the RIR database for the space.661 of 673
ROA: none101.193.244.0/22No ROA covers it. Add a ROA for AS402279, maxLength 22.661 of 673
Route object: none101.193.244.0/22Route objects for it name AS53587, AS62573, AS135091. Add a route object with origin AS402279 in the RIR database for the space.661 of 673
ROA: none101.193.248.0/22No ROA covers it. Add a ROA for AS402279, maxLength 22.661 of 673
Route object: none101.193.248.0/22Route objects for it name AS53587, AS62573, AS135091. Add a route object with origin AS402279 in the RIR database for the space.661 of 673
ROA: none208.66.228.0/23No ROA covers it. Add a ROA for AS402279, maxLength 23.2 of 673
Route object: none208.66.228.0/23No route object for it. Add a route object with origin AS402279 in the RIR database for the space.2 of 673

Route objects not announced

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

101.193.224.0/22RADBNo ROA
103.27.76.0/22APNICValid
103.27.76.0/23APNICValid
103.27.76.0/24APNICValid
103.27.77.0/24APNICValid
103.27.78.0/23APNICValid
103.27.78.0/24APNICValid
103.27.79.0/24APNICValid
169.40.140.0/24RADB, RIPEValid
2602:f486:f4::/48ARINValid
2602:f486:f5::/48ARINValid
2602:f486:f6::/48ARINValid
2602:f486:f7::/48ARINValid
2602:f486:f8::/48ARINValid
2602:f486:f9::/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.