bgpreport

Network · data from 2026-11-12

AS134428 Edge Cloud Globe

Registry name: ECG-AS-AP - Edge Cloud Globe Co., Limited, HK · PeeringDB

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

Announced routes

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

103.211.70.0/24 No ROA Other origin only 2 0%low visibility 2
115.42.63.0/24 No ROA Other origin only 2 0%low visibility 2
125.62.68.0/24 Valid RIR databaseAPNIC 672 100% 67
125.62.69.0/24 Valid RIR databaseAPNIC 672 100% 67
125.62.70.0/24 Valid RIR databaseAPNIC 672 100% 67
125.62.71.0/24 Valid RIR databaseAPNIC 672 100% 67

AS-SET

PeeringDB's irr_as_set for AS134428: RADB::AS-ECGL. 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 (AS134428 isn't in the set, or no route object for AS134428 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 objectsAS134428 in itNot covered
RADB::AS-ECGL RADBlists itself further down3 member sets in no database: AS-REDUCED, AS139855:AS-ALL, AS212233:AS-ECHK 188462 Yes 2

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 15 are in fix.csv.

  • ROA: none2
  • Route object: none2
  • AS-SET: missing member3
  • Route object: not announced8
ChangePrefix or setDetailFull-table peers
ROA: none103.211.70.0/24No ROA covers it. Add a ROA for AS134428, maxLength 24.2 of 673
Route object: none103.211.70.0/24Route objects for it name AS38197, AS64050. Add a route object with origin AS134428 in the RIR database for the space.2 of 673
ROA: none115.42.63.0/24No ROA covers it. Add a ROA for AS134428, maxLength 24.2 of 673
Route object: none115.42.63.0/24Route objects for it name AS38197, AS64050. Add a route object with origin AS134428 in the RIR database for the space.2 of 673
AS-SET: missing memberRADB::AS-ECGLAS-ECGL (RADB) lists AS-REDUCED; no IRR database read has it.
AS-SET: missing memberRADB::AS-ECGLAS-ECGL (RADB) lists AS139855:AS-ALL; no IRR database read has it.
AS-SET: missing memberRADB::AS-ECGLAS-ECGL (RADB) lists AS212233:AS-ECHK; no IRR database read has it.

Route objects not announced

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

103.84.44.0/22RADBNo ROA
103.136.148.0/22RADBNo ROA
103.136.148.0/23RADBNo ROA
103.158.160.0/23RADBNo ROA
103.204.180.0/24RADBNo ROA
156.240.100.0/23RADBNo ROA
193.5.25.0/24RADBNo ROA
203.147.240.0/21RADBNo 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.