Network · data from 2026-11-12
AS131183 EPNET-AS-AP - Empowering Net (epnet)
Registry name: EPNET-AS-AP - Empowering Net (epnet), BD · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS131183, 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.136.106.0/24 | Invalid: origin | Other origin only | 0 0%low visibility |
| 103.137.75.0/24 | Invalid: origin | Other origin only | 0 0%low visibility |
| 103.111.35.0/24 | Valid | RIR databaseAPNIC | 673 100% |
| 103.136.104.0/24 | Valid | RIR databaseAPNIC | 673 100% |
| 103.136.105.0/24 | Valid | RIR databaseAPNIC | 673 100% |
| 103.103.239.0/24 | Valid | RIR databaseAPNIC | 671 100% |
| 103.111.34.0/24 | Valid | RIR databaseAPNIC | 671 100% |
| 103.111.36.0/24 | Valid | RIR databaseAPNIC | 671 100% |
| 2402:9dc0::/36 | Valid | RIR databaseAPNIC | 636 100% |
| 2402:9dc0:1000::/36 | Valid | RIR databaseAPNIC | 636 100% |
| 2402:9dc0:2000::/36 | Valid | RIR databaseAPNIC | 636 100% |
| 2402:9dc0:3000::/36 | Valid | RIR databaseAPNIC | 636 100% |
| 2402:9dc0:4000::/36 | Valid | RIR databaseAPNIC | 636 100% |
| 2402:9dc0:5000::/36 | Valid | RIR databaseAPNIC | 636 100% |
| 2402:9dc0:6000::/36 | Valid | RIR databaseAPNIC | 636 100% |
| 2402:9dc0:7000::/36 | Valid | RIR databaseAPNIC | 636 100% |
| 2402:9dc0:8000::/36 | Valid | RIR databaseAPNIC | 636 100% |
| 2402:9dc0:9000::/36 | Valid | RIR databaseAPNIC | 636 100% |
| 2402:9dc0:a000::/36 | Valid | RIR databaseAPNIC | 636 100% |
| 2402:9dc0:b000::/36 | Valid | RIR databaseAPNIC | 636 100% |
| 2402:9dc0:c000::/36 | Valid | RIR databaseAPNIC | 636 100% |
| 2402:9dc0:d000::/36 | Valid | RIR databaseAPNIC | 636 100% |
| 2402:9dc0:e000::/36 | Valid | RIR databaseAPNIC | 636 100% |
| 2402:9dc0:f000::/36 | Valid | RIR databaseAPNIC | 636 100% |
AS-SET
AS131183 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 8 are in fix.csv.
- ROA: origin2
- Route object: none2
- Route object: not announced4
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: origin | 103.136.106.0/24 | ROAs covering it name AS139282, not AS131183. If AS131183 should announce it, add a ROA for AS131183. |
| Route object: none | 103.136.106.0/24 | Route objects for it name AS139282. Add a route object with origin AS131183 in the RIR database for the space. |
| ROA: origin | 103.137.75.0/24 | ROAs covering it name AS139282, not AS131183. If AS131183 should announce it, add a ROA for AS131183. |
| Route object: none | 103.137.75.0/24 | Route objects for it name AS139282. Add a route object with origin AS131183 in the RIR database for the space. |
Route objects not announced
Route objects with origin AS131183 whose prefix no peer sees AS131183 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 103.111.34.0/23 | APNIC | Valid |
| 2402:9dc0::/32 | APNIC | Valid |
| 2404:90c0::/48 | APNIC | Valid |
| 2404:90c0:2::/48 | APNIC | 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.