Network · data from 2026-11-12
AS45410 ALLO, City Broadband Service
Registry name: ALLOTECH-AS-MY - ALLO TECHNOLOGY SDN. BHD., MY · PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS45410, 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.
| 2401:b780:68::/48 | Valid | Nonecovered by 2401:b780::/32 | 332 52% |
| 2401:b780:69::/48 | Valid | Nonecovered by 2401:b780::/32 | 332 52% |
| 2401:b780:5000::/48 | Valid | Nonecovered by 2401:b780::/32 | 332 52% |
| 2401:b780:5002::/48 | Valid | Nonecovered by 2401:b780::/32 | 332 52% |
| 2401:b780:5003::/48 | Valid | Nonecovered by 2401:b780::/32 | 332 52% |
| 2401:b780:5010::/48 | Valid | Nonecovered by 2401:b780::/32 | 332 52% |
| 2401:b780:5011::/48 | Valid | Nonecovered by 2401:b780::/32 | 332 52% |
| 2401:b780:5012::/48 | Valid | Nonecovered by 2401:b780::/32 | 332 52% |
| 2401:b780:2000::/48 | Valid | Nonecovered by 2401:b780::/32 | 331 52% |
| 2401:b780::/32 | Valid | Other IRR onlyRADB | 636 100% |
| 163.61.92.0/23 | Valid | RIR databaseAPNIC | 673 100% |
| 202.168.64.0/20 | Valid | RIR databaseAPNIC, NTTCOM, RADB | 673 100% |
| 202.168.67.0/24 | Valid | RIR databaseAPNIC, NTTCOM, RADB | 671 100% |
| 202.168.74.0/24 | Valid | RIR databaseAPNIC, NTTCOM, RADB | 671 100% |
| 202.168.76.0/24 | Valid | RIR databaseAPNIC, NTTCOM, RADB | 671 100% |
| 202.168.78.0/24 | Valid | RIR databaseAPNIC, NTTCOM, RADB | 671 100% |
| 202.168.79.0/24 | Valid | RIR databaseAPNIC, NTTCOM, RADB | 671 100% |
| 202.168.68.0/24 | Valid | RIR databaseAPNIC, NTTCOM, RADB | 670 100% |
| 202.168.72.0/24 | Valid | RIR databaseAPNIC, NTTCOM, RADB | 670 100% |
| 202.168.64.0/24 | Valid | RIR databaseAPNIC, NTTCOM, RADB | 152 23% |
| 202.168.65.0/24 | Valid | RIR databaseAPNIC, NTTCOM, RADB | 152 23% |
| 202.168.66.0/24 | Valid | RIR databaseAPNIC, NTTCOM, RADB | 152 23% |
| 202.168.69.0/24 | Valid | RIR databaseAPNIC, NTTCOM, RADB | 152 23% |
| 202.168.70.0/24 | Valid | RIR databaseAPNIC, NTTCOM, RADB | 152 23% |
| 202.168.71.0/24 | Valid | RIR databaseAPNIC, NTTCOM, RADB | 152 23% |
| 202.168.73.0/24 | Valid | RIR databaseAPNIC, NTTCOM, RADB | 152 23% |
| 202.168.75.0/24 | Valid | RIR databaseAPNIC, NTTCOM, RADB | 152 23% |
AS-SET
PeeringDB's irr_as_set for AS45410: AS-CBJAYABBAND. 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 (AS45410 isn't in the set, or no route object for AS45410 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 | AS45410 in it | Not covered |
|---|---|---|---|---|---|
| AS-CBJAYABBAND | APNIC | 6 | 1 | 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 27 are in fix.csv.
- Route object: none9
- Route object: RIR1
- Route object: not announced17
| Change | Prefix or set | Detail |
|---|---|---|
| Route object: none | 2401:b780:68::/48 | No route object for it. A route object for 2401:b780::/32 with origin AS45410 covers it (filters allowing more-specifics accept it). Add a route object with origin AS45410 in the RIR database for the space. |
| Route object: none | 2401:b780:69::/48 | No route object for it. A route object for 2401:b780::/32 with origin AS45410 covers it (filters allowing more-specifics accept it). Add a route object with origin AS45410 in the RIR database for the space. |
| Route object: none | 2401:b780:5000::/48 | No route object for it. A route object for 2401:b780::/32 with origin AS45410 covers it (filters allowing more-specifics accept it). Add a route object with origin AS45410 in the RIR database for the space. |
| Route object: none | 2401:b780:5002::/48 | No route object for it. A route object for 2401:b780::/32 with origin AS45410 covers it (filters allowing more-specifics accept it). Add a route object with origin AS45410 in the RIR database for the space. |
| Route object: none | 2401:b780:5003::/48 | No route object for it. A route object for 2401:b780::/32 with origin AS45410 covers it (filters allowing more-specifics accept it). Add a route object with origin AS45410 in the RIR database for the space. |
| Route object: none | 2401:b780:5010::/48 | No route object for it. A route object for 2401:b780::/32 with origin AS45410 covers it (filters allowing more-specifics accept it). Add a route object with origin AS45410 in the RIR database for the space. |
| Route object: none | 2401:b780:5011::/48 | No route object for it. A route object for 2401:b780::/32 with origin AS45410 covers it (filters allowing more-specifics accept it). Add a route object with origin AS45410 in the RIR database for the space. |
| Route object: none | 2401:b780:5012::/48 | No route object for it. A route object for 2401:b780::/32 with origin AS45410 covers it (filters allowing more-specifics accept it). Add a route object with origin AS45410 in the RIR database for the space. |
| Route object: none | 2401:b780:2000::/48 | No route object for it. A route object for 2401:b780::/32 with origin AS45410 covers it (filters allowing more-specifics accept it). Add a route object with origin AS45410 in the RIR database for the space. |
| Route object: RIR | 2401:b780::/32 | Route object only in RADB. Add it in the RIR database for the space. |
Route objects not announced
Route objects with origin AS45410 whose prefix no peer sees AS45410 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 163.61.92.0/24 | APNIC | Valid |
| 163.61.93.0/24 | APNIC | Valid |
| 202.168.64.0/21 | APNIC, NTTCOM, RADB | Valid |
| 202.168.64.0/22 | APNIC, NTTCOM, RADB | Valid |
| 202.168.64.0/23 | APNIC, NTTCOM, RADB | Valid |
| 202.168.66.0/23 | APNIC, NTTCOM, RADB | Valid |
| 202.168.68.0/22 | APNIC, NTTCOM, RADB | Valid |
| 202.168.68.0/23 | APNIC, NTTCOM, RADB | Valid |
| 202.168.70.0/23 | APNIC, NTTCOM, RADB | Valid |
| 202.168.72.0/21 | APNIC, NTTCOM, RADB | Valid |
| 202.168.72.0/22 | APNIC, NTTCOM, RADB | Valid |
| 202.168.72.0/23 | APNIC, NTTCOM, RADB | Valid |
| 202.168.74.0/23 | APNIC, NTTCOM, RADB | Valid |
| 202.168.76.0/22 | APNIC, NTTCOM, RADB | Valid |
| 202.168.76.0/23 | APNIC, NTTCOM, RADB | Valid |
| 202.168.77.0/24 | APNIC, NTTCOM, RADB | Valid |
| 202.168.78.0/23 | APNIC, NTTCOM, 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.