bgpreport

Network · data from 2026-11-12

AS211585 MaiyunZhang

Registry name: MAIYUN Maiyun Zhang, US · PeeringDB

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

Announced routes

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

2a0f:6282:2100::/44 No ROA None 1 0%low visibility 1
44.30.70.0/24 No ROA Other IRR onlyRADB 668 99% 67
2a0f:6282:210a::/48 Valid RIR databaseRIPE 636 100% 67
2a0f:6282:210b::/48 Valid RIR databaseRIPE 636 100% 67
2001:67c:878::/48 Valid RIR databaseALTDB, RIPE 634 100% 69
2602:f92a:1316::/48 Valid RIR databaseARIN 633 100% 69
2a0f:6282:2108::/47 Valid RIR databaseRIPE 633 100% 68
2a0f:6282:2100::/45 Valid RIR databaseRIPE 2 0%low visibility 2

AS-SET

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

  • ROA: none2
  • Route object: none1
  • Route object: RIR1
  • Route object: not announced2
ChangePrefix or setDetailFull-table peers
ROA: none2a0f:6282:2100::/44No ROA covers it. Add a ROA for AS211585, maxLength 44.1 of 636
Route object: none2a0f:6282:2100::/44No route object for it. Add a route object with origin AS211585 in the RIR database for the space.1 of 636
ROA: none44.30.70.0/24No ROA covers it. Add a ROA for AS211585, maxLength 24.668 of 673
Route object: RIR44.30.70.0/24Route object only in RADB. Add it in the RIR database for the space.668 of 673

Route objects not announced

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

216.185.60.0/24ARINInvalid: origin
2a0f:6282:210c::/46RIPEValid

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.