bgpreport

Network · data from 2026-11-12

AS136251 EDTCL-HK - EVERY DAY TECHNOLOGY CO. LIMITED

Registry name: EDTCL-HK - EVERY DAY TECHNOLOGY CO. LIMITED, HK · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS136251, 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.204.180.0/22 No ROA Other origin only 436 65% 66
202.181.0.0/22 No ROA Other origin only 436 65% 66
210.79.61.0/24 Valid RIR databaseAPNIC 671 100% 67
210.79.62.0/24 Valid RIR databaseAPNIC 671 100% 67
210.79.63.0/24 Valid RIR databaseAPNIC 671 100% 67

AS-SET

AS136251 isn't in PeeringDB, where networks name their AS-SET.

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

  • ROA: none2
  • Route object: none2
ChangePrefix or setDetailFull-table peers
ROA: none103.204.180.0/22No ROA covers it. Add a ROA for AS136251, maxLength 22.436 of 673
Route object: none103.204.180.0/22Route objects for it name AS133115, AS138571. Add a route object with origin AS136251 in the RIR database for the space.436 of 673
ROA: none202.181.0.0/22No ROA covers it. Add a ROA for AS136251, maxLength 22.436 of 673
Route object: none202.181.0.0/22Route objects for it name AS7545, AS133115, AS138571. Add a route object with origin AS136251 in the RIR database for the space.436 of 673

Route objects not announced

Every route object with origin AS136251 is announced.

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.