Network · data from 2026-11-12
AS150288 METAGE-AS-AP - METAGE TECHNOLOGY PTE. LTD.
Registry name: METAGE-AS-AP - METAGE TECHNOLOGY PTE. LTD., SG · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS150288, 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.104.151.0/24 | Valid | Other IRR onlyRADB | 673 100% |
| 103.129.139.0/24 | Valid | Other IRR onlyRADB | 673 100% |
| 211.79.98.0/24 | Valid | Other IRR onlyRADB | 673 100% |
| 103.135.116.0/24 | Valid | Other IRR onlyRADB | 672 100% |
| 103.135.117.0/24 | Valid | Other IRR onlyRADB | 672 100% |
| 202.148.216.0/24 | Valid | Other IRR onlyRADB | 672 100% |
| 103.129.136.0/23 | Valid | Other IRR onlyRADB | 671 100% |
| 103.129.138.0/24 | Valid | Other IRR onlyRADB | 671 100% |
| 202.148.217.0/24 | Valid | Other IRR onlyRADB | 671 100% |
| 103.135.118.0/24 | Valid | Other IRR onlyRADB | 520 77% |
| 103.135.119.0/24 | Valid | Other IRR onlyRADB | 520 77% |
| 103.129.136.0/24 | Valid | Other IRR onlyRADB | 4 1%low visibility |
| 103.129.137.0/24 | Valid | Other IRR onlyRADB | 4 1%low visibility |
| 103.126.142.0/24 | Valid | RIR databaseAPNIC | 671 100% |
| 103.126.143.0/24 | Valid | RIR databaseAPNIC | 671 100% |
AS-SET
AS150288 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 25 are in fix.csv.
- Route object: RIR13
- Route object: not announced12
| Change | Prefix or set | Detail |
|---|---|---|
| Route object: RIR | 103.104.151.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 103.129.139.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 211.79.98.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 103.135.116.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 103.135.117.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 202.148.216.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 103.129.136.0/23 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 103.129.138.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 202.148.217.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 103.135.118.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 103.135.119.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 103.129.136.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 103.129.137.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
Route objects not announced
Route objects with origin AS150288 whose prefix no peer sees AS150288 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 103.126.142.0/23 | APNIC | Valid |
| 103.129.136.0/22 | RADB | Valid |
| 103.129.138.0/23 | RADB | Valid |
| 103.135.116.0/22 | RADB | Valid |
| 103.135.116.0/23 | RADB | Valid |
| 103.135.118.0/23 | RADB | Valid |
| 202.148.216.0/23 | RADB | Valid |
| 211.79.96.0/23 | RADB | No ROA |
| 211.79.96.0/24 | RADB | No ROA |
| 211.79.97.0/24 | RADB | No ROA |
| 211.79.98.0/23 | RADB | Valid |
| 211.79.99.0/24 | 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.