bgpreport

Network · data from 2026-11-12

AS200936 Chengjie Guo's Experimental Network (AS200936)

Registry name: GUO-AS Chengjie Guo, CN · PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS200936, 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:1cc5:1901::/48 No ROA RIR databaseRIPE 635 100% 70
2a0f:1cc5:1902::/48 No ROA RIR databaseRIPE 1 0%low visibility 1
2a0a:6040:d619::/48 Valid RIR databaseRIPE 636 100% 67
2a0a:6040:d611::/48 Valid RIR databaseRIPE 635 100% 67
2a0a:6040:d613::/48 Valid RIR databaseRIPE 635 100% 69
2a0a:6040:d623::/48 Valid RIR databaseRIPE 635 100% 69
2a0a:6040:d629::/48 Valid RIR databaseRIPE 635 100% 69
2a0a:6040:d610::/48 Valid RIR databaseRIPE 634 100% 69
2a0a:6040:d616::/48 Valid RIR databaseRIPE 634 100% 69
2a0a:6040:d618::/48 Valid RIR databaseRIPE 634 100% 69
2a0a:6040:d624::/48 Valid RIR databaseRIPE 633 100% 69
2a0a:6040:d615::/48 Valid RIR databaseRIPE 616 97% 69
2a0f:9400:6110::/48 Valid RIR databaseRIPE 43 7%low visibility 17
2a0a:6040:d600::/44 Valid RIR databaseRADB, RIPE 3 0%low visibility 3
2a0a:6040:d626::/48 Valid RIR databaseRIPE 1 0%low visibility 1
2a0a:6040:d630::/48 Valid RIR databaseRIPE 1 0%low visibility 1

AS-SET

PeeringDB's irr_as_set for AS200936: AS200936:AS-GEECLOUD. 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 (AS200936 isn't in the set, or no route object for AS200936 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 objectsAS200936 in itNot covered
AS200936:AS-GEECLOUD RIPE 1132 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 18 are in fix.csv.

  • ROA: none2
  • Route object: not announced16
ChangePrefix or setDetailFull-table peers
ROA: none2a0f:1cc5:1901::/48No ROA covers it. Add a ROA for AS200936, maxLength 48.635 of 636
ROA: none2a0f:1cc5:1902::/48No ROA covers it. Add a ROA for AS200936, maxLength 48.1 of 636

Route objects not announced

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

2a0a:6040:d600::/40RIPEValid
2a0a:6040:d612::/48RIPEValid
2a0a:6040:d614::/48RIPEValid
2a0a:6040:d617::/48RIPEValid
2a0a:6040:d620::/48RIPEValid
2a0a:6040:d621::/48RIPEValid
2a0a:6040:d622::/48RIPEValid
2a0a:6040:d625::/48RIPEValid
2a0a:6040:d627::/48RIPEValid
2a0a:6040:d628::/48RIPEValid
2a0a:6040:d631::/48RIPEValid
2a0a:6040:d632::/48RIPEValid
2a0a:6040:d633::/48RIPEValid
2a0a:6040:d634::/48RIPEValid
2a0a:6040:d635::/48RIPEValid
2a0f:1cc5:1900::/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.