bgpreport

Network · data from 2026-11-12

AS206628 EzriCloud

Registry name: EzriCloud Tianyu-Zhu, US · PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS206628, 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:fd50:20::/48 No ROA RIR databaseARIN 634 100% 69
198.8.59.0/24 Valid RIR databaseARIN 672 100% 67
198.8.58.0/24 Valid RIR databaseARIN 670 100% 68
2a0f:85c1:31::/48 Valid RIR databaseRIPE 636 100% 69
2001:678:d3c::/48 Valid RIR databaseRIPE 634 100% 69
2a0f:85c1:30::/48 Valid RIR databaseRIPE 634 100% 69

AS-SET

PeeringDB's irr_as_set for AS206628: AS206628:AS-EZRICLOUD. 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 (AS206628 isn't in the set, or no route object for AS206628 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 objectsAS206628 in itNot covered
AS206628:AS-EZRICLOUD RIPElists itself further down8 member sets in no database: AS-EVAN-PRATTEN, AS-IPV6GO, AS-SHIZUKUGLOBAL-EUROPE, AS-SVINE, AS-TUNNELBROKERIO … 131496,352 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 11 are in fix.csv.

  • ROA: none1
  • AS-SET: missing member8
  • Route object: not announced2
ChangePrefix or setDetailFull-table peers
ROA: none2602:fd50:20::/48No ROA covers it. Add a ROA for AS206628, maxLength 48.634 of 636
AS-SET: missing memberAS206628:AS-EZRICLOUDAS206628:AS-EZRICLOUD (RIPE) lists AS-EVAN-PRATTEN; no IRR database read has it.
AS-SET: missing memberAS206628:AS-EZRICLOUDAS206628:AS-EZRICLOUD (RIPE) lists AS-IPV6GO; no IRR database read has it.
AS-SET: missing memberAS206628:AS-EZRICLOUDAS206628:AS-EZRICLOUD (RIPE) lists AS-SHIZUKUGLOBAL-EUROPE; no IRR database read has it.
AS-SET: missing memberAS206628:AS-EZRICLOUDAS206628:AS-EZRICLOUD (RIPE) lists AS-SVINE; no IRR database read has it.
AS-SET: missing memberAS206628:AS-EZRICLOUDAS206628:AS-EZRICLOUD (RIPE) lists AS-TUNNELBROKERIO; no IRR database read has it.
AS-SET: missing memberAS206628:AS-EZRICLOUDAS206628:AS-EZRICLOUD (RIPE) lists AS-ZH-NET; no IRR database read has it.
AS-SET: missing memberAS206628:AS-EZRICLOUDAS206628:AS-EZRICLOUD (RIPE) lists AS200372:AS-DORFHOSTER-SET; no IRR database read has it.
AS-SET: missing memberAS206628:AS-EZRICLOUDAS206628:AS-EZRICLOUD (RIPE) lists AS212516:AS-ALESSIOCAIROLI; no IRR database read has it.

Route objects not announced

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

2a0f:85c1:21::/48RIPEValid
2a0f:85c1:22::/48RIPEValid

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.