Network · data from 2026-11-12
AS136781 DEDE-AS-AP - Department of Alternative Energy Development and Efficiency
Registry name: DEDE-AS-AP - Department of Alternative Energy Development and Efficiency, TH · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS136781, 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.
| 2403:6200:7907::/48 | Invalid: origin | None | 1 0%low visibility |
| 2401:7140::/32 | Valid | None | 635 100% |
| 103.95.228.0/22 | Valid | RIR databaseAPNIC | 673 100% |
AS-SET
AS136781 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 9 are in fix.csv.
- ROA: origin1
- Route object: none2
- Route object: not announced6
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: origin | 2403:6200:7907::/48 | ROAs covering it name AS45629, AS45758, not AS136781. If AS136781 should announce it, add a ROA for AS136781. |
| Route object: none | 2403:6200:7907::/48 | No route object for it. Add a route object with origin AS136781 in the RIR database for the space. |
| Route object: none | 2401:7140::/32 | No route object for it. Add a route object with origin AS136781 in the RIR database for the space. |
Route objects not announced
Route objects with origin AS136781 whose prefix no peer sees AS136781 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 103.95.228.0/23 | APNIC | Valid |
| 103.95.228.0/24 | APNIC, RADB | Valid |
| 103.95.229.0/24 | APNIC, RADB | Valid |
| 103.95.230.0/23 | APNIC | Valid |
| 103.95.230.0/24 | APNIC, RADB | Valid |
| 103.95.231.0/24 | APNIC, RADB | Valid |
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.