Network · data from 2026-11-12
AS19148 LeaseWeb / PHX-01
Registry name: LEASEWEB-USA-PHX - Leaseweb USA, Inc., US · PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS19148, 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.
| 23.19.108.0/22 | Valid | RIR databaseARIN, RADB | 673 100% |
| 23.19.132.0/22 | Valid | RIR databaseARIN, RADB | 673 100% |
| 23.19.144.0/22 | Valid | RIR databaseARIN, RADB | 673 100% |
| 23.19.172.0/22 | Valid | RIR databaseARIN, RADB | 673 100% |
| 23.81.16.0/21 | Valid | RIR databaseARIN, RADB | 673 100% |
| 23.81.48.0/20 | Valid | RIR databaseARIN, RADB | 673 100% |
| 23.81.80.0/22 | Valid | RIR databaseARIN, RADB | 673 100% |
| 23.81.88.0/21 | Valid | RIR databaseARIN, RADB | 673 100% |
| 23.81.120.0/21 | Valid | RIR databaseARIN, RADB | 673 100% |
| 23.81.128.0/21 | Valid | RIR databaseARIN, RADB | 673 100% |
| 23.81.144.0/21 | Valid | RIR databaseARIN, RADB | 673 100% |
| 23.81.172.0/22 | Valid | RIR databaseARIN, RADB | 673 100% |
| 23.81.192.0/21 | Valid | RIR databaseARIN, RADB | 673 100% |
| 23.81.204.0/22 | Valid | RIR databaseARIN | 673 100% |
| 23.81.216.0/22 | Valid | RIR databaseARIN | 673 100% |
| 23.81.224.0/19 | Valid | RIR databaseARIN, RADB | 673 100% |
| 23.81.252.0/22 | Valid | RIR databaseARIN | 673 100% |
| 23.82.60.0/22 | Valid | RIR databaseARIN, RADB | 673 100% |
| 23.82.152.0/21 | Valid | RIR databaseARIN | 673 100% |
| 23.83.128.0/21 | Valid | RIR databaseARIN, RADB | 673 100% |
| 23.83.144.0/21 | Valid | RIR databaseARIN, RADB | 673 100% |
| 23.83.184.0/22 | Valid | RIR databaseARIN, RADB | 673 100% |
| 23.105.56.0/21 | Valid | RIR databaseARIN | 673 100% |
| 64.120.56.0/21 | Valid | RIR databaseARIN | 673 100% |
| 64.120.72.0/22 | Valid | RIR databaseARIN, RADB | 673 100% |
| 64.120.124.0/22 | Valid | RIR databaseARIN | 673 100% |
| 89.249.194.0/24 | Valid | RIR databaseRADB, RIPE | 673 100% |
| 89.249.195.0/24 | Valid | RIR databaseRADB, RIPE | 673 100% |
| 108.62.16.0/21 | Valid | RIR databaseARIN | 673 100% |
| 108.62.144.0/21 | Valid | RIR databaseARIN | 673 100% |
| 108.62.224.0/21 | Valid | RIR databaseARIN | 673 100% |
| 152.163.48.0/22 | Valid | RIR databaseRIPE | 673 100% |
| 152.163.76.0/22 | Valid | RIR databaseRIPE | 673 100% |
| 152.163.124.0/22 | Valid | RIR databaseRIPE | 673 100% |
| 152.163.152.0/22 | Valid | RIR databaseRIPE | 673 100% |
| 152.163.176.0/22 | Valid | RIR databaseRIPE | 673 100% |
| 152.163.200.0/22 | Valid | RIR databaseRIPE | 673 100% |
| 152.163.228.0/22 | Valid | RIR databaseRIPE | 673 100% |
| 152.163.252.0/22 | Valid | RIR databaseRIPE | 673 100% |
| 173.208.64.0/22 | Valid | RIR databaseARIN, RADB | 673 100% |
| 173.208.127.0/24 | Valid | RIR databaseARIN | 673 100% |
| 191.101.26.0/24 | Valid | RIR databaseRADB, RIPE | 673 100% |
| 191.101.174.0/24 | Valid | RIR databaseRADB, RIPE | 673 100% |
| 212.42.196.0/24 | Valid | RIR databaseRADB, RIPE | 673 100% |
| 212.42.206.0/24 | Valid | RIR databaseRADB, RIPE | 673 100% |
| 2607:f5b0::/32 | Valid | RIR databaseARIN, RADB | 635 100% |
| 2a11:2340::/29 | Valid | RIR databaseRIPE | 632 99% |
| 2a11:3940::/29 | Valid | RIR databaseRIPE | 632 99% |
| 2a11:50c0::/29 | Valid | RIR databaseRIPE | 632 99% |
| 2a11:7540::/29 | Valid | RIR databaseRIPE | 632 99% |
| 2a11:9440::/29 | Valid | RIR databaseRIPE | 632 99% |
| 2a11:a440::/29 | Valid | RIR databaseRIPE | 632 99% |
| 2a11:c140::/29 | Valid | RIR databaseRIPE | 632 99% |
| 2a11:dc40::/29 | Valid | RIR databaseRIPE | 632 99% |
| 2a12:6400::/29 | Valid | RIR databaseRIPE | 632 99% |
| 2a12:b600::/29 | Valid | RIR databaseRIPE | 632 99% |
| 2607:f5b5:3::/48 | Valid | RIR databaseARIN | 98 15% |
| 2607:f5b5:2::/48 | Valid | RIR databaseARIN | 97 15% |
| 23.19.52.0/24 | Valid | RIR databaseARIN | 59 9%low visibility |
| 23.19.53.0/24 | Valid | RIR databaseARIN | 59 9%low visibility |
AS-SET
PeeringDB's irr_as_set for AS19148: AS19148. 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 (AS19148 isn't in the set, or no route object for AS19148 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 | AS19148 in it | Not covered | |
|---|---|---|---|---|---|---|
| AS19148 | A single AS number, not a set: AS19148 (this network), 60 route objects. | |||||
Fix list
Nothing to change: every route is RPKI valid with a route object in an RIR database, and every route object is announced.
Route objects not announced
Every route object with origin AS19148 is announced.
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.