Network · data from 2026-11-12
AS134707 RoyalCable
Registry name: RCC-AS-AP - RoyalCable Flash, PH · PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS134707, 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.121.80.0/24 | Invalid: origin | Other origin only | 1 0%low visibility |
| 149.30.128.0/19 | No ROA | Other IRR onlyRADB | 673 100% |
| 103.196.136.0/22 | Valid | RIR databaseAPNIC | 673 100% |
| 203.189.116.0/22 | Valid | RIR databaseAPNIC | 673 100% |
| 223.25.60.0/22 | Valid | RIR databaseAPNIC | 669 99% |
| 2404:3380::/32 | Valid | RIR databaseAPNIC | 636 100% |
AS-SET
PeeringDB's irr_as_set for AS134707: AS134707:AS-ROYALCABLE. 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 (AS134707 isn't in the set, or no route object for AS134707 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 | AS134707 in it | Not covered |
|---|---|---|---|---|---|
| AS134707:AS-ROYALCABLE | APNIC | 19 | 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 17 are in fix.csv.
- ROA: origin1
- ROA: none1
- Route object: none1
- Route object: RIR1
- Route object: not announced13
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: origin | 103.121.80.0/24 | ROAs covering it name AS138147, not AS134707. If AS134707 should announce it, add a ROA for AS134707. |
| Route object: none | 103.121.80.0/24 | Route objects for it name AS138147. Add a route object with origin AS134707 in the RIR database for the space. |
| ROA: none | 149.30.128.0/19 | No ROA covers it. Add a ROA for AS134707, maxLength 19. |
| Route object: RIR | 149.30.128.0/19 | Route object only in RADB. Add it in the RIR database for the space. |
Route objects not announced
Route objects with origin AS134707 whose prefix no peer sees AS134707 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 103.196.136.0/24 | APNIC | Valid |
| 103.196.137.0/24 | APNIC | Valid |
| 103.196.138.0/24 | APNIC | Valid |
| 103.196.139.0/24 | APNIC | Valid |
| 203.189.116.0/24 | APNIC | Valid |
| 203.189.117.0/24 | APNIC | Valid |
| 203.189.118.0/24 | APNIC | Valid |
| 203.189.119.0/24 | APNIC | Valid |
| 223.25.60.0/24 | APNIC | Valid |
| 223.25.61.0/24 | APNIC | Valid |
| 223.25.62.0/24 | APNIC | Valid |
| 223.25.63.0/24 | APNIC | Valid |
| 2406:a240::/32 | APNIC | 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.