Network · data from 2026-11-12
AS131711 PT Global Teknologi Teraindo
Registry name: ORANGE-ISP-AS-ID - PT Global Teknologi Teraindo, ID · PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS131711, 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.9.124.0/24 | Valid | Other origin onlycovered by 103.9.124.0/23 | 673 100% |
| 103.9.125.0/24 | Valid | Nonecovered by 103.9.124.0/23 | 673 100% |
| 103.9.126.0/24 | Valid | Nonecovered by 103.9.126.0/23 | 673 100% |
| 103.9.127.0/24 | Valid | Nonecovered by 103.9.126.0/23 | 673 100% |
| 45.251.73.0/24 | Valid | Other IRR onlyNTTCOM, RADB | 673 100% |
| 45.251.74.0/23 | Valid | Other IRR onlyNTTCOM | 673 100% |
| 45.251.74.0/24 | Valid | Other IRR onlyNTTCOM, RADB | 673 100% |
| 45.251.75.0/24 | Valid | Other IRR onlyNTTCOM, RADB | 673 100% |
| 103.9.124.0/23 | Valid | Other IRR onlyRADB | 673 100% |
| 103.9.126.0/23 | Valid | Other IRR onlyNTTCOM, RADB | 673 100% |
| 45.251.72.0/22 | Valid | RIR databaseAPNIC, RADB | 673 100% |
| 45.251.72.0/23 | Valid | RIR databaseAPNIC | 673 100% |
| 45.251.72.0/24 | Valid | RIR databaseAPNIC, RADB | 673 100% |
| 103.9.124.0/22 | Valid | RIR databaseAPNIC | 673 100% |
| 2402:1d20::/32 | Valid | RIR databaseAPNIC, RADB | 635 100% |
| 2402:1d20::/48 | Valid | RIR databaseAPNIC, RADB | 635 100% |
| 2402:1d20:72::/48 | Valid | RIR databaseAPNIC, RADB | 635 100% |
| 2402:1d20:73::/48 | Valid | RIR databaseAPNIC, RADB | 635 100% |
| 2402:1d20:74::/48 | Valid | RIR databaseAPNIC, RADB | 635 100% |
| 2402:1d20:75::/48 | Valid | RIR databaseAPNIC, RADB | 635 100% |
| 2402:1d20:124::/48 | Valid | RIR databaseAPNIC, RADB | 635 100% |
| 2402:1d20:125::/48 | Valid | RIR databaseAPNIC, RADB | 635 100% |
| 2402:1d20:126::/48 | Valid | RIR databaseAPNIC, RADB | 635 100% |
| 2402:1d20:127::/48 | Valid | RIR databaseAPNIC, RADB | 635 100% |
AS-SET
PeeringDB's irr_as_set for AS131711: AS131711:AS-ORANGE-ISP. 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 (AS131711 isn't in the set, or no route object for AS131711 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 | AS131711 in it | Not covered |
|---|---|---|---|---|---|
| AS131711:AS-ORANGE-ISP | RADB | 11 | 1 | Yes | 0 |
| ALTDB (also) | 10 | 1 | Yes | 0 | |
| APNIC (also) | 10 | 1 | Yes | 0 |
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 11 are in fix.csv.
- Route object: none4
- Route object: RIR6
- Route object: not announced1
| Change | Prefix or set | Detail |
|---|---|---|
| Route object: none | 103.9.124.0/24 | Route objects for it name AS23947. A route object for 103.9.124.0/23 with origin AS131711 covers it (filters allowing more-specifics accept it). Add a route object with origin AS131711 in the RIR database for the space. |
| Route object: none | 103.9.125.0/24 | No route object for it. A route object for 103.9.124.0/23 with origin AS131711 covers it (filters allowing more-specifics accept it). Add a route object with origin AS131711 in the RIR database for the space. |
| Route object: none | 103.9.126.0/24 | No route object for it. A route object for 103.9.126.0/23 with origin AS131711 covers it (filters allowing more-specifics accept it). Add a route object with origin AS131711 in the RIR database for the space. |
| Route object: none | 103.9.127.0/24 | No route object for it. A route object for 103.9.126.0/23 with origin AS131711 covers it (filters allowing more-specifics accept it). Add a route object with origin AS131711 in the RIR database for the space. |
| Route object: RIR | 45.251.73.0/24 | Route object only in NTTCOM, RADB. Add it in the RIR database for the space. |
| Route object: RIR | 45.251.74.0/23 | Route object only in NTTCOM. Add it in the RIR database for the space. |
| Route object: RIR | 45.251.74.0/24 | Route object only in NTTCOM, RADB. Add it in the RIR database for the space. |
| Route object: RIR | 45.251.75.0/24 | Route object only in NTTCOM, RADB. Add it in the RIR database for the space. |
| Route object: RIR | 103.9.124.0/23 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 103.9.126.0/23 | Route object only in NTTCOM, RADB. Add it in the RIR database for the space. |
Route objects not announced
Route objects with origin AS131711 whose prefix no peer sees AS131711 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 103.193.14.0/23 | RADB | No ROA |
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.