Network · data from 2026-11-12
AS13959 AUTOPHONE-OF-LAREDO - Autophone of Laredo
Registry name: AUTOPHONE-OF-LAREDO - Autophone of Laredo, US · not in PeeringDB
12IPv4 routes
100.0% RPKI valid · 0.0% with a route object
0IPv6 routes
0RPKI invalid
0 origin · 0 maxLength
0No ROA
12 with no route object for this origin
0Low visibility
seen by under 10% of full-table peers
5Route objects not announced
registered with origin AS13959, seen from no peer
Announced routes
Every prefix a peer of the route collectors sees with origin AS13959, 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.
| 216.150.32.0/24 | Valid | Nonecovered by 216.150.32.0/20 | 673 100% |
| 216.150.33.0/24 | Valid | Nonecovered by 216.150.32.0/20 | 673 100% |
| 216.150.34.0/24 | Valid | Nonecovered by 216.150.32.0/20 | 673 100% |
| 216.150.35.0/24 | Valid | Nonecovered by 216.150.32.0/20 | 673 100% |
| 216.150.36.0/24 | Valid | Nonecovered by 216.150.32.0/20 | 673 100% |
| 216.150.40.0/24 | Valid | Nonecovered by 216.150.32.0/20 | 673 100% |
| 216.150.41.0/24 | Valid | Nonecovered by 216.150.32.0/20 | 673 100% |
| 216.150.42.0/24 | Valid | Nonecovered by 216.150.32.0/20 | 673 100% |
| 216.150.43.0/24 | Valid | Nonecovered by 216.150.32.0/20 | 672 100% |
| 216.150.45.0/24 | Valid | Nonecovered by 216.150.32.0/20 | 672 100% |
| 216.150.46.0/24 | Valid | Nonecovered by 216.150.32.0/20 | 672 100% |
| 216.150.47.0/24 | Valid | Nonecovered by 216.150.32.0/20 | 672 100% |
AS-SET
AS13959 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 17 are in fix.csv.
- Route object: none12
- Route object: not announced5
| Change | Prefix or set | Detail |
|---|---|---|
| Route object: none | 216.150.32.0/24 | No route object for it. A route object for 216.150.32.0/20 with origin AS13959 covers it (filters allowing more-specifics accept it). Add a route object with origin AS13959 in the RIR database for the space. |
| Route object: none | 216.150.33.0/24 | No route object for it. A route object for 216.150.32.0/20 with origin AS13959 covers it (filters allowing more-specifics accept it). Add a route object with origin AS13959 in the RIR database for the space. |
| Route object: none | 216.150.34.0/24 | No route object for it. A route object for 216.150.32.0/20 with origin AS13959 covers it (filters allowing more-specifics accept it). Add a route object with origin AS13959 in the RIR database for the space. |
| Route object: none | 216.150.35.0/24 | No route object for it. A route object for 216.150.32.0/20 with origin AS13959 covers it (filters allowing more-specifics accept it). Add a route object with origin AS13959 in the RIR database for the space. |
| Route object: none | 216.150.36.0/24 | No route object for it. A route object for 216.150.32.0/20 with origin AS13959 covers it (filters allowing more-specifics accept it). Add a route object with origin AS13959 in the RIR database for the space. |
| Route object: none | 216.150.40.0/24 | No route object for it. A route object for 216.150.32.0/20 with origin AS13959 covers it (filters allowing more-specifics accept it). Add a route object with origin AS13959 in the RIR database for the space. |
| Route object: none | 216.150.41.0/24 | No route object for it. A route object for 216.150.32.0/20 with origin AS13959 covers it (filters allowing more-specifics accept it). Add a route object with origin AS13959 in the RIR database for the space. |
| Route object: none | 216.150.42.0/24 | No route object for it. A route object for 216.150.32.0/20 with origin AS13959 covers it (filters allowing more-specifics accept it). Add a route object with origin AS13959 in the RIR database for the space. |
| Route object: none | 216.150.43.0/24 | No route object for it. A route object for 216.150.32.0/20 with origin AS13959 covers it (filters allowing more-specifics accept it). Add a route object with origin AS13959 in the RIR database for the space. |
| Route object: none | 216.150.45.0/24 | No route object for it. A route object for 216.150.32.0/20 with origin AS13959 covers it (filters allowing more-specifics accept it). Add a route object with origin AS13959 in the RIR database for the space. |
| Route object: none | 216.150.46.0/24 | No route object for it. A route object for 216.150.32.0/20 with origin AS13959 covers it (filters allowing more-specifics accept it). Add a route object with origin AS13959 in the RIR database for the space. |
| Route object: none | 216.150.47.0/24 | No route object for it. A route object for 216.150.32.0/20 with origin AS13959 covers it (filters allowing more-specifics accept it). Add a route object with origin AS13959 in the RIR database for the space. |
Route objects not announced
Route objects with origin AS13959 whose prefix no peer sees AS13959 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 45.7.44.0/22 | LACNIC, RADB | Valid |
| 45.167.12.0/22 | LACNIC | Valid |
| 216.150.32.0/20 | RADB | No ROA |
| 2806:2e6::/32 | LACNIC, RADB | Valid |
| 2806:311::/32 | LACNIC | 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.