Network · data from 2026-11-12
AS133876 ESECURE-AS-AP - e-secure Pty Ltd
Registry name: ESECURE-AS-AP - e-secure Pty Ltd, AU · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS133876, 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.
| 101.97.52.0/30 | Invalid: origin | None | 1 0%low visibility |
| 103.44.148.0/24 | Valid | RIR databaseAPNIC, NTTCOM | 672 100% |
| 203.16.202.0/24 | Valid | RIR databaseAPNIC, NTTCOM | 672 100% |
| 203.16.203.0/24 | Valid | RIR databaseAPNIC, NTTCOM | 672 100% |
| 203.16.200.0/24 | Valid | RIR databaseAPNIC, NTTCOM | 671 100% |
| 203.16.201.0/24 | Valid | RIR databaseAPNIC, NTTCOM, RADB | 671 100% |
| 2400:bf20::/36 | Valid | RIR databaseAPNIC, NTTCOM, RADB | 636 100% |
| 2400:bf20:1000::/36 | Valid | RIR databaseAPNIC, NTTCOM, RADB | 636 100% |
AS-SET
AS133876 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 6 are in fix.csv.
- ROA: origin1
- Route object: none1
- Route object: not announced4
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: origin | 101.97.52.0/30 | ROAs covering it name AS15830, not AS133876. If AS133876 should announce it, add a ROA for AS133876. |
| Route object: none | 101.97.52.0/30 | No route object for it. Add a route object with origin AS133876 in the RIR database for the space. |
Route objects not announced
Route objects with origin AS133876 whose prefix no peer sees AS133876 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 2001:df5:c300::/48 | NTTCOM | No ROA |
| 2400:bf20::/32 | RADB | No ROA |
| 2400:bf20:2000::/36 | APNIC, NTTCOM, RADB | Valid |
| 2400:bf20:3000::/36 | APNIC, NTTCOM, 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.