Network · data from 2026-11-12
AS59288 NET Sentra Cyberindo AS59288
Registry name: IDNIC-NETSENTRA-AS-ID - PT Net Sentra Cyberindo, ID · PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS59288, 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.84.10.0/24 | No ROA | Other IRR onlyRADB | 671 100% |
| 27.0.199.0/24 | Valid | Other IRR onlyNTTCOM | 670 100% |
| 103.229.163.0/24 | Valid | Other IRR onlyNTTCOM, RADB, REACH | 670 100% |
AS-SET
PeeringDB's irr_as_set for AS59288: AS59288. 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 (AS59288 isn't in the set, or no route object for AS59288 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.
| Name | Database | ASNs | Sets | AS59288 in it | Not covered | |
|---|---|---|---|---|---|---|
| AS59288 | A single AS number, not a set: AS59288 (this network), 17 route objects. | |||||
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 18 are in fix.csv.
- ROA: none1
- Route object: RIR3
- Route object: not announced14
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 103.84.10.0/24 | No ROA covers it. Add a ROA for AS59288, maxLength 24. |
| Route object: RIR | 103.84.10.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 27.0.199.0/24 | Route object only in NTTCOM. Add it in the RIR database for the space. |
| Route object: RIR | 103.229.163.0/24 | Route object only in NTTCOM, RADB, REACH. Add it in the RIR database for the space. |
Route objects not announced
Route objects with origin AS59288 whose prefix no peer sees AS59288 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 27.0.196.0/22 | NTTCOM | Valid |
| 27.0.196.0/23 | NTTCOM | Valid |
| 27.0.196.0/24 | NTTCOM, RADB | Valid |
| 27.0.197.0/24 | NTTCOM, RADB | Valid |
| 27.0.198.0/23 | NTTCOM | Valid |
| 27.0.198.0/24 | NTTCOM | Valid |
| 103.84.8.0/24 | RADB | No ROA |
| 103.84.9.0/24 | RADB | No ROA |
| 103.229.160.0/22 | NTTCOM | Valid |
| 103.229.160.0/23 | NTTCOM, RADB | Valid |
| 103.229.160.0/24 | NTTCOM, RADB, REACH | Valid |
| 103.229.161.0/24 | NTTCOM, RADB, REACH | Valid |
| 103.229.162.0/23 | NTTCOM | Valid |
| 103.229.162.0/24 | NTTCOM, REACH | 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.