bgpreport

Network · data from 2026-11-12

AS141221 Ekwinox Network Project

Registry name: EKWINOX-AS-AP - Equinox, aka ekwinox. My favorite time-space coordinate., HK · PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS141221, 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:feda:aeb::/48 No ROA Other IRR onlyALTDB 635 100% 68
2602:feda:cde::/48 No ROA RIR databaseARIN 635 100% 68
2602:feda:cdc::/48 No ROA RIR databaseARIN 633 100% 69

AS-SET

PeeringDB's irr_as_set for AS141221: RIPE::AS-EKWINOX. 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 (AS141221 isn't in the set, or no route object for AS141221 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 objectsAS141221 in itNot covered
RIPE::AS-EKWINOX RIPE 127 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 8 are in fix.csv.

  • ROA: none3
  • Route object: RIR1
  • Route object: not announced4
ChangePrefix or setDetailFull-table peers
ROA: none2602:feda:aeb::/48No ROA covers it. Add a ROA for AS141221, maxLength 48.635 of 636
Route object: RIR2602:feda:aeb::/48Route object only in ALTDB. Add it in the RIR database for the space.635 of 636
ROA: none2602:feda:cde::/48No ROA covers it. Add a ROA for AS141221, maxLength 48.635 of 636
ROA: none2602:feda:cdc::/48No ROA covers it. Add a ROA for AS141221, maxLength 48.633 of 636

Route objects not announced

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

2602:feda:cd0::/44ARINNo ROA
2602:feda:cdd::/48ARINNo ROA
2a0e:b107:e11::/48RIPENo ROA
2a0e:b107:e12::/48RIPENo 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.