Network · data from 2026-11-12
AS14500 Galaxy Broadband Communications
Registry name: GALAXYBROADBAND-01 - Galaxy Broadband Communications Inc., CA · PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS14500, 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.
| 2607:72c0:100::/48 | Valid | Nonecovered by 2607:72c0:100::/40 | 635 100% |
| 2607:72c0:200::/48 | Valid | Nonecovered by 2607:72c0:200::/40 | 635 100% |
| 68.70.144.0/22 | Valid | RIR databaseARIN | 673 100% |
| 68.70.152.0/22 | Valid | RIR databaseARIN | 673 100% |
| 68.70.156.0/22 | Valid | RIR databaseARIN | 673 100% |
| 173.244.80.0/22 | Valid | RIR databaseARIN | 672 100% |
| 68.70.148.0/22 | Valid | RIR databaseARIN | 671 100% |
| 173.244.84.0/22 | Valid | RIR databaseARIN | 671 100% |
| 173.244.87.0/24 | Valid | RIR databaseARIN | 671 100% |
| 192.151.132.0/23 | Valid | RIR databaseARIN | 671 100% |
| 173.244.88.0/21 | Valid | RIR databaseARIN | 669 99% |
| 173.244.94.0/24 | Valid | RIR databaseARIN | 667 99% |
| 192.151.134.0/23 | Valid | RIR databaseARIN | 667 99% |
| 199.182.116.0/22 | Valid | RIR databaseARIN | 667 99% |
| 192.151.132.0/24 | Valid | RIR databaseARIN | 20 3%low visibility |
AS-SET
PeeringDB's irr_as_set for AS14500: AS14500:AS-CONE. 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 (AS14500 isn't in the set, or no route object for AS14500 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 | AS14500 in it | Not covered |
|---|---|---|---|---|---|
| AS14500:AS-CONE | ARIN | 2 | 2 | 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 7 are in fix.csv.
- Route object: none2
- Route object: not announced5
| Change | Prefix or set | Detail |
|---|---|---|
| Route object: none | 2607:72c0:100::/48 | No route object for it. A route object for 2607:72c0:100::/40 with origin AS14500 covers it (filters allowing more-specifics accept it). Add a route object with origin AS14500 in the RIR database for the space. |
| Route object: none | 2607:72c0:200::/48 | No route object for it. A route object for 2607:72c0:200::/40 with origin AS14500 covers it (filters allowing more-specifics accept it). Add a route object with origin AS14500 in the RIR database for the space. |
Route objects not announced
Route objects with origin AS14500 whose prefix no peer sees AS14500 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 2607:72c0::/40 | ARIN | Valid |
| 2607:72c0:100::/40 | ARIN | Valid |
| 2607:72c0:200::/40 | ARIN | Valid |
| 2607:72c0:300::/40 | ARIN | Valid |
| 2607:72c0:1000::/36 | ARIN | 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.