bgpreport

Network · data from 2026-11-12

AS62246 WJY Limited

Registry name: WJY-AS WJY Limited, GB · PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS62246, 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.235.105.0/24 Valid Nonecovered by 66.235.104.0/22 673 100% 66
66.235.104.0/24 Valid Nonecovered by 66.235.104.0/22 2 0%low visibility 2
66.235.107.0/24 Valid RIR databaseARIN 673 100% 67
199.188.198.0/24 Valid RIR databaseARIN 673 100% 67
66.235.104.0/22 Valid RIR databaseARIN 671 100% 67
199.188.199.0/24 Valid RIR databaseARIN 669 99% 66
2a13:a5c0:100::/40 Valid RIR databaseRIPE 636 100% 69
2a13:a5c0::/40 Valid RIR databaseRIPE 635 100% 69
2a13:a5c0:200::/40 Valid RIR databaseALTDB, RADB, RIPE 634 100% 69
2a13:a5c0:400::/40 Valid RIR databaseRIPE 633 100% 69
2a13:a5c0:500::/40 Valid RIR databaseRIPE 632 99% 69
66.235.106.0/23 Valid RIR databaseARIN 495 74% 67
66.235.106.0/24 Valid RIR databaseARIN 86 13% 43
2a13:a5c0:300::/40 Valid RIR databaseRIPE 2 0%low visibility 3

AS-SET

PeeringDB's irr_as_set for AS62246: AS-WJY. Expanded from the day's IRR dumps the way bgpq4 does against whois.radb.net: a name with a database is read from that database only, one without from the first database in RADB's order. "Not covered" = this network's own routes that a filter built from the set would leave out (AS62246 isn't in the set, or no route object for AS62246 covers the route; more-specifics of a route object are accepted down to /24 and /48, as with bgpq4 -A -R 24 / -R 48). Customers' routes aren't counted: the collectors show each route's origin, not which network it came through.

NameDatabaseASNsSets Route objectsAS62246 in itNot covered
AS-WJY RIPE 2021,289 Yes 0
APNIC (also)1 member set in no database: AS62246:AS-DOWNSTREAMS 41100 Yes 0
ARIN (also)1 member set in no database: AS62246:AS-DOWNSTREAMS 41100 Yes 0

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

  • Route object: none2
  • Route object: not announced3
ChangePrefix or setDetailFull-table peers
Route object: none66.235.105.0/24No route object for it. A route object for 66.235.104.0/22 with origin AS62246 covers it (filters allowing more-specifics accept it). Add a route object with origin AS62246 in the RIR database for the space.673 of 673
Route object: none66.235.104.0/24No route object for it. A route object for 66.235.104.0/22 with origin AS62246 covers it (filters allowing more-specifics accept it). Add a route object with origin AS62246 in the RIR database for the space.2 of 673

Route objects not announced

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

2a13:a5c0::/32RIPEValid
2a13:a5c0:600::/40RIPEValid
2a13:a5c0:700::/40RIPEValid

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.