Network · data from 2026-11-12
AS45718 Surya Global Teknologi
Registry name: JURAGAN-AS-ID - PT Surya Global Teknologi, ID · PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS45718, 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.31.206.0/24 | Valid | Other IRR onlyREACH | 673 100% |
| 103.198.93.0/24 | Valid | Other IRR onlyNTTCOM, RADB, REACH | 673 100% |
| 117.103.66.0/24 | Valid | Other IRR onlyNTTCOM, RADB, REACH | 673 100% |
| 203.79.29.0/24 | Valid | Other IRR onlyNTTCOM, RADB, REACH | 673 100% |
AS-SET
PeeringDB's irr_as_set for AS45718: AS45718. 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 (AS45718 isn't in the set, or no route object for AS45718 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 | AS45718 in it | Not covered | |
|---|---|---|---|---|---|---|
| AS45718 | A single AS number, not a set: AS45718 (this network), 15 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 15 are in fix.csv.
- Route object: RIR4
- Route object: not announced11
| Change | Prefix or set | Detail |
|---|---|---|
| Route object: RIR | 103.31.206.0/24 | Route object only in REACH. Add it in the RIR database for the space. |
| Route object: RIR | 103.198.93.0/24 | Route object only in NTTCOM, RADB, REACH. Add it in the RIR database for the space. |
| Route object: RIR | 117.103.66.0/24 | Route object only in NTTCOM, RADB, REACH. Add it in the RIR database for the space. |
| Route object: RIR | 203.79.29.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 AS45718 whose prefix no peer sees AS45718 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 59.153.82.0/24 | REACH | Invalid: origin |
| 59.153.83.0/24 | REACH | Invalid: origin |
| 103.31.204.0/23 | RADB | Valid |
| 103.31.204.0/24 | RADB | Valid |
| 103.31.205.0/24 | RADB | Valid |
| 103.38.216.0/23 | RADB | No ROA |
| 117.103.64.0/22 | RADB | No ROA |
| 117.103.65.0/24 | REACH | Invalid: origin |
| 117.103.66.0/23 | NTTCOM, RADB | Valid |
| 117.103.67.0/24 | RADB | Valid |
| 2001:df0:b3::/48 | 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.