Network · data from 2026-11-12
AS38278 ORIENT TELECOMS
Registry name: OTSB-AS-AP - Orient Telecoms Sdn. Bhd, MY · PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS38278, 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.115.220.0/22 | No ROA | None | 109 16% |
| 103.251.0.0/24 | Valid | Other IRR onlyNTTCOM, RADB | 673 100% |
| 103.251.2.0/24 | Valid | Other IRR onlyNTTCOM, RADB | 673 100% |
| 111.221.48.0/24 | Valid | Other IRR onlyRADB | 673 100% |
| 111.221.50.0/24 | Valid | Other IRR onlyRADB | 673 100% |
| 111.221.51.0/24 | Valid | Other IRR onlyRADB | 673 100% |
| 111.221.53.0/24 | Valid | Other IRR onlyRADB | 673 100% |
| 111.221.54.0/24 | Valid | Other IRR onlyRADB | 673 100% |
| 45.114.28.0/22 | Valid | RIR databaseAPNIC, NTTCOM, RADB | 673 100% |
| 103.248.108.0/22 | Valid | RIR databaseAPNIC | 673 100% |
| 103.251.0.0/22 | Valid | RIR databaseAPNIC, NTTCOM, RADB | 673 100% |
| 111.221.48.0/21 | Valid | RIR databaseAPNIC, NTTCOM, RADB | 673 100% |
| 202.169.24.0/21 | Valid | RIR databaseAPNIC, NTTCOM, RADB | 673 100% |
| 202.169.24.0/22 | Valid | RIR databaseAPNIC, NTTCOM, RADB | 673 100% |
| 202.169.24.0/24 | Valid | RIR databaseAPNIC, RADB | 673 100% |
| 202.169.25.0/24 | Valid | RIR databaseAPNIC, RADB | 673 100% |
| 202.169.26.0/24 | Valid | RIR databaseAPNIC, RADB | 673 100% |
| 202.169.27.0/24 | Valid | RIR databaseAPNIC, RADB | 673 100% |
| 202.169.28.0/22 | Valid | RIR databaseAPNIC, RADB | 673 100% |
| 202.169.28.0/24 | Valid | RIR databaseAPNIC, RADB | 673 100% |
| 202.169.29.0/24 | Valid | RIR databaseAPNIC, RADB | 673 100% |
| 202.169.30.0/24 | Valid | RIR databaseAPNIC, RADB | 673 100% |
| 202.169.31.0/24 | Valid | RIR databaseAPNIC, RADB | 673 100% |
| 2402:eec0::/32 | Valid | RIR databaseAPNIC | 636 100% |
AS-SET
PeeringDB's irr_as_set for AS38278: AS-ORIENT-MY. 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 (AS38278 isn't in the set, or no route object for AS38278 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 | AS38278 in it | Not covered |
|---|---|---|---|---|---|
| AS-ORIENT-MY | APNIC | 6 | 1 | Yes | 1 |
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 36 are in fix.csv.
- ROA: none1
- Route object: none1
- Route object: RIR7
- Route object: not announced27
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 103.115.220.0/22 | No ROA covers it. Add a ROA for AS38278, maxLength 22. |
| Route object: none | 103.115.220.0/22 | No route object for it. Add a route object with origin AS38278 in the RIR database for the space. |
| Route object: RIR | 103.251.0.0/24 | Route object only in NTTCOM, RADB. Add it in the RIR database for the space. |
| Route object: RIR | 103.251.2.0/24 | Route object only in NTTCOM, RADB. Add it in the RIR database for the space. |
| Route object: RIR | 111.221.48.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 111.221.50.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 111.221.51.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 111.221.53.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 111.221.54.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
Route objects not announced
Route objects with origin AS38278 whose prefix no peer sees AS38278 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 103.115.220.0/24 | APNIC | Valid |
| 103.115.221.0/24 | APNIC | Valid |
| 103.115.222.0/24 | APNIC | Valid |
| 103.115.223.0/24 | APNIC | Valid |
| 103.248.108.0/23 | APNIC | Valid |
| 103.248.108.0/24 | APNIC | Valid |
| 103.248.109.0/24 | APNIC | Valid |
| 103.248.110.0/23 | APNIC | Valid |
| 103.248.110.0/24 | APNIC | Valid |
| 103.248.111.0/24 | APNIC | Valid |
| 103.251.0.0/23 | NTTCOM, RADB | Valid |
| 103.251.1.0/24 | NTTCOM, RADB | Valid |
| 103.251.2.0/23 | NTTCOM, RADB | Valid |
| 103.251.3.0/24 | NTTCOM, RADB | Valid |
| 111.221.48.0/22 | RADB | Valid |
| 111.221.48.0/23 | RADB | Valid |
| 111.221.49.0/24 | RADB | Valid |
| 111.221.50.0/23 | RADB | Valid |
| 111.221.52.0/22 | RADB | Valid |
| 111.221.52.0/23 | RADB | Valid |
| 111.221.52.0/24 | RADB | Valid |
| 111.221.54.0/23 | RADB | Valid |
| 111.221.55.0/24 | RADB | Valid |
| 202.169.24.0/23 | APNIC, RADB | Valid |
| 202.169.26.0/23 | APNIC, RADB | Valid |
| 202.169.28.0/23 | APNIC, RADB | Valid |
| 202.169.30.0/23 | APNIC, 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.