bgpreport

Network · data from 2026-11-12

AS209565 CandyRect Network

Registry name: CANDYRECT-NET Shanghai Candy Rectangle Technology Co., Ltd., CN · PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS209565, 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.

2a12:cb40:1::/48 Invalid: origin RIR databaseRIPE 2 0%low visibility 2
2a12:cb40:2::/48 Invalid: origin RIR databaseRIPE 2 0%low visibility 2

AS-SET

PeeringDB's irr_as_set for AS209565: RIPE::AS209565: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 (AS209565 isn't in the set, or no route object for AS209565 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 objectsAS209565 in itNot covered
RIPE::AS209565:AS-ALL RIPE 134 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 4 are in fix.csv.

  • ROA: origin2
  • Route object: not announced2
ChangePrefix or setDetailFull-table peers
ROA: origin2a12:cb40:1::/48ROAs covering it name AS10977, AS199605, AS215172, not AS209565. If AS209565 should announce it, add a ROA for AS209565.2 of 636
ROA: origin2a12:cb40:2::/48ROAs covering it name AS10977, AS199605, AS215172, not AS209565. If AS209565 should announce it, add a ROA for AS209565.2 of 636

Route objects not announced

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

2a0f:1cc5:ffff::/48RIPENo ROA
2a12:cb45::/32RIPEInvalid: origin

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.