Network · data from 2026-11-12
AS136216 BPOSEATS-COM-AS-AP - Channel Information Technology Support and Leasing Services Inc.
Registry name: BPOSEATS-COM-AS-AP - Channel Information Technology Support and Leasing Services Inc., PH · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS136216, 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.83.224.0/22 | No ROA | RIR databaseAPNIC | 672 100% |
AS-SET
AS136216 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 7 are in fix.csv.
- ROA: none1
- Route object: not announced6
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 103.83.224.0/22 | No ROA covers it. Add a ROA for AS136216, maxLength 22. |
Route objects not announced
Route objects with origin AS136216 whose prefix no peer sees AS136216 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 103.83.224.0/23 | APNIC | No ROA |
| 103.83.224.0/24 | APNIC | No ROA |
| 103.83.225.0/24 | APNIC | No ROA |
| 103.83.226.0/23 | APNIC | No ROA |
| 103.83.226.0/24 | APNIC, RADB | No ROA |
| 103.83.227.0/24 | APNIC | 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.