bgpreport

Network · data from 2026-11-12

AS202610 NekoClaw Ltd

Registry name: NEKO-AS NekoClaw Ltd, GB · PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS202610, 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.
194.55.224.0/24 Invalid: origin None 2 0%low visibility 2
144.31.231.0/24 Valid RIR databaseRIPE 672 100% 66
2a0d:d940:6c0::/42 Valid RIR databaseRIPE 636 100% 67
2a0d:d940:90a5::/48 Valid RIR databaseRIPE 634 100% 68

AS-SET

PeeringDB's irr_as_set for AS202610: AS202610:AS-ALL. 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 (AS202610 isn't in the set, or no route object for AS202610 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 objectsAS202610 in itNot covered
AS202610:AS-ALL RIPE 3130 Yes 1

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

  • ROA: origin1
  • Route object: none1
ChangePrefix or setDetailFull-table peers
ROA: origin194.55.224.0/24An AS0 ROA covers it (the holder's statement that it shouldn't be routed). If AS202610 should announce it, add a ROA for AS202610.2 of 673
Route object: none194.55.224.0/24No route object for it. Add a route object with origin AS202610 in the RIR database for the space.2 of 673

Route objects not announced

Every route object with origin AS202610 is announced.

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.