bgpreport

Network · data from 2026-11-12

AS202335 Haima Network

Registry name: HAIMA-AS Zhanrui Tian, CN · PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS202335, 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:cb47:ffff::/48 Valid Other origin only 122 19% 42
2a0f:1cc5:2600::/42 Valid RIR databaseRIPE 636 100% 69
2a0f:1cc5:2608::/45 Valid RIR databaseRIPE 636 100% 69
2a0f:1cc5:2648::/46 Valid RIR databaseRIPE 636 100% 67
2a0f:1cc5:2600::/45 Valid RIR databaseRIPE 635 100% 67
2a0f:1cc5:260b::/48 Valid RIR databaseRIPE 635 100% 69
2a0f:1cc5:2610::/45 Valid RIR databaseRIPE 634 100% 69
2a0f:1cc5:2640::/42 Valid RIR databaseRIPE 634 100% 69
2a0f:1cc5:2640::/45 Valid RIR databaseRIPE 634 100% 69
2a0f:1cc5:2650::/44 Valid RIR databaseRIPE 634 100% 69
2a0f:1cc5:2680::/42 Valid RIR databaseRIPE 629 99% 69
2a0f:1cc5:2680::/46 Valid RIR databaseRIPE 629 99% 69
2a0f:1cc5:264c::/46 Valid RIR databaseRIPE 1 0%low visibility 1

AS-SET

PeeringDB's irr_as_set for AS202335: RIPE::AS202335:AS-DOWNSTREAM. 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 (AS202335 isn't in the set, or no route object for AS202335 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 objectsAS202335 in itNot covered
RIPE::AS202335:AS-DOWNSTREAM RIPE2 member sets in no database: AS-MOEDOVE-BN, AS150184:AS-OWO 2221 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 9 are in fix.csv.

  • Route object: none1
  • AS-SET: missing member2
  • Route object: not announced6
ChangePrefix or setDetailFull-table peers
Route object: none2a12:cb47:ffff::/48Route objects for it name AS202734, AS204211, AS207529, AS211575. Add a route object with origin AS202335 in the RIR database for the space.122 of 636
AS-SET: missing memberRIPE::AS202335:AS-DOWNSTREAMAS202335:AS-DOWNSTREAM (RIPE) lists AS-MOEDOVE-BN; no IRR database read has it.
AS-SET: missing memberRIPE::AS202335:AS-DOWNSTREAMAS202335:AS-DOWNSTREAM (RIPE) lists AS150184:AS-OWO; no IRR database read has it.

Route objects not announced

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

2602:feda:bf0::/44ARINInvalid: origin
2a0f:1cc5:2600::/40RIPEValid
2a0f:1cc5:26c0::/42RIPEValid
2a0f:1cc5:26c0::/44RIPEValid
2a0f:1cc5:26c8::/45RIPEValid
2a0f:1cc7:ff19::/48RADB, RIPEValid

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.