Network · data from 2026-11-12
AS59282 PT Giga Patra Multimedia
Registry name: GPM-AS-ID - PT Giga Patra Multimedia, ID · PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS59282, 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.254.104.0/23 | Valid | Nonecovered by 103.254.104.0/22 | 668 99% |
| 103.254.106.0/23 | Valid | Nonecovered by 103.254.104.0/22 | 668 99% |
| 202.74.76.0/23 | Valid | Nonecovered by 202.74.76.0/22 | 668 99% |
| 202.74.78.0/23 | Valid | Nonecovered by 202.74.76.0/22 | 668 99% |
| 2400:d680:2::/48 | Valid | Nonecovered by 2400:d680::/32 | 636 100% |
| 103.228.244.0/22 | Valid | Other IRR onlyNTTCOM, RADB | 673 100% |
| 103.254.104.0/22 | Valid | Other IRR onlyRADB | 673 100% |
| 116.206.212.0/22 | Valid | Other IRR onlyNTTCOM, RADB | 673 100% |
| 202.74.76.0/22 | Valid | Other IRR onlyRADB | 673 100% |
| 103.228.244.0/23 | Valid | Other IRR onlyNTTCOM | 668 99% |
| 103.228.244.0/24 | Valid | Other IRR onlyNTTCOM, RADB | 668 99% |
| 103.228.245.0/24 | Valid | Other IRR onlyNTTCOM, RADB | 668 99% |
| 103.228.246.0/23 | Valid | Other IRR onlyNTTCOM | 668 99% |
| 103.228.246.0/24 | Valid | Other IRR onlyNTTCOM, RADB | 668 99% |
| 103.228.247.0/24 | Valid | Other IRR onlyNTTCOM, RADB | 668 99% |
| 116.206.212.0/23 | Valid | Other IRR onlyNTTCOM | 668 99% |
| 116.206.212.0/24 | Valid | Other IRR onlyNTTCOM, RADB | 668 99% |
| 116.206.213.0/24 | Valid | Other IRR onlyNTTCOM, RADB | 668 99% |
| 116.206.214.0/23 | Valid | Other IRR onlyNTTCOM | 668 99% |
| 116.206.214.0/24 | Valid | Other IRR onlyNTTCOM, RADB | 668 99% |
| 116.206.215.0/24 | Valid | Other IRR onlyNTTCOM, RADB | 668 99% |
| 2400:d680:59::/48 | Valid | Other IRR onlyRADB | 636 100% |
| 2400:d680:face::/48 | Valid | Other IRR onlyRADB | 634 100% |
| 103.254.105.0/24 | Valid | RIR databaseAPNIC, RADB | 673 100% |
| 103.254.104.0/24 | Valid | RIR databaseAPNIC, RADB | 668 99% |
| 103.254.106.0/24 | Valid | RIR databaseAPNIC, RADB | 668 99% |
| 103.254.107.0/24 | Valid | RIR databaseAPNIC, RADB | 668 99% |
| 202.74.76.0/24 | Valid | RIR databaseAPNIC, RADB | 668 99% |
| 202.74.77.0/24 | Valid | RIR databaseAPNIC, RADB | 668 99% |
| 202.74.78.0/24 | Valid | RIR databaseAPNIC, RADB | 668 99% |
| 202.74.79.0/24 | Valid | RIR databaseAPNIC, RADB | 668 99% |
AS-SET
PeeringDB's irr_as_set for AS59282: AS59282:AS-GPM. 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 (AS59282 isn't in the set, or no route object for AS59282 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 | AS59282 in it | Not covered |
|---|---|---|---|---|---|
| AS59282:AS-GPM | RADB | 15 | 2 | 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 28 are in fix.csv.
- Route object: none5
- Route object: RIR18
- Route object: not announced5
| Change | Prefix or set | Detail |
|---|---|---|
| Route object: none | 103.254.104.0/23 | No route object for it. A route object for 103.254.104.0/22 with origin AS59282 covers it (filters allowing more-specifics accept it). Add a route object with origin AS59282 in the RIR database for the space. |
| Route object: none | 103.254.106.0/23 | No route object for it. A route object for 103.254.104.0/22 with origin AS59282 covers it (filters allowing more-specifics accept it). Add a route object with origin AS59282 in the RIR database for the space. |
| Route object: none | 202.74.76.0/23 | No route object for it. A route object for 202.74.76.0/22 with origin AS59282 covers it (filters allowing more-specifics accept it). Add a route object with origin AS59282 in the RIR database for the space. |
| Route object: none | 202.74.78.0/23 | No route object for it. A route object for 202.74.76.0/22 with origin AS59282 covers it (filters allowing more-specifics accept it). Add a route object with origin AS59282 in the RIR database for the space. |
| Route object: none | 2400:d680:2::/48 | No route object for it. A route object for 2400:d680::/32 with origin AS59282 covers it (filters allowing more-specifics accept it). Add a route object with origin AS59282 in the RIR database for the space. |
| Route object: RIR | 103.228.244.0/22 | Route object only in NTTCOM, RADB. Add it in the RIR database for the space. |
| Route object: RIR | 103.254.104.0/22 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 116.206.212.0/22 | Route object only in NTTCOM, RADB. Add it in the RIR database for the space. |
| Route object: RIR | 202.74.76.0/22 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 103.228.244.0/23 | Route object only in NTTCOM. Add it in the RIR database for the space. |
| Route object: RIR | 103.228.244.0/24 | Route object only in NTTCOM, RADB. Add it in the RIR database for the space. |
| Route object: RIR | 103.228.245.0/24 | Route object only in NTTCOM, RADB. Add it in the RIR database for the space. |
| Route object: RIR | 103.228.246.0/23 | Route object only in NTTCOM. Add it in the RIR database for the space. |
| Route object: RIR | 103.228.246.0/24 | Route object only in NTTCOM, RADB. Add it in the RIR database for the space. |
| Route object: RIR | 103.228.247.0/24 | Route object only in NTTCOM, RADB. Add it in the RIR database for the space. |
| Route object: RIR | 116.206.212.0/23 | Route object only in NTTCOM. Add it in the RIR database for the space. |
| Route object: RIR | 116.206.212.0/24 | Route object only in NTTCOM, RADB. Add it in the RIR database for the space. |
| Route object: RIR | 116.206.213.0/24 | Route object only in NTTCOM, RADB. Add it in the RIR database for the space. |
| Route object: RIR | 116.206.214.0/23 | Route object only in NTTCOM. Add it in the RIR database for the space. |
| Route object: RIR | 116.206.214.0/24 | Route object only in NTTCOM, RADB. Add it in the RIR database for the space. |
| Route object: RIR | 116.206.215.0/24 | Route object only in NTTCOM, RADB. Add it in the RIR database for the space. |
| Route object: RIR | 2400:d680:59::/48 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 2400:d680:face::/48 | Route object only in RADB. Add it in the RIR database for the space. |
Route objects not announced
Route objects with origin AS59282 whose prefix no peer sees AS59282 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 103.161.134.0/23 | RADB | Valid |
| 103.161.134.0/24 | RADB | Valid |
| 103.161.135.0/24 | RADB | Valid |
| 2400:d680::/32 | RADB | Valid |
| 2400:d680:6::/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.