Network · data from 2026-11-12
AS270026 RED SERVITEL
Registry name: AS270026 - RED SERVITEL, CA, VE · PeeringDB
34IPv4 routes
100.0% RPKI valid · 14.7% with a route object
6IPv6 routes
100.0% RPKI valid · 0.0% with a route object
0RPKI invalid
0 origin · 0 maxLength
0No ROA
35 with no route object for this origin
1Low visibility
seen by under 10% of full-table peers
7Route objects not announced
registered with origin AS270026, seen from no peer
Announced routes
Every prefix a peer of the route collectors sees with origin AS270026, 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.
| 38.172.164.0/22 | Valid | Nonecovered by 38.172.160.0/19 | 673 100% |
| 38.172.168.0/22 | Valid | Nonecovered by 38.172.160.0/19 | 673 100% |
| 38.172.172.0/22 | Valid | Nonecovered by 38.172.160.0/19 | 673 100% |
| 38.172.164.0/24 | Valid | Nonecovered by 38.172.160.0/19 | 672 100% |
| 38.172.165.0/24 | Valid | Nonecovered by 38.172.160.0/19 | 672 100% |
| 38.172.166.0/24 | Valid | Nonecovered by 38.172.160.0/19 | 672 100% |
| 38.172.167.0/24 | Valid | Nonecovered by 38.172.160.0/19 | 672 100% |
| 38.172.168.0/24 | Valid | Nonecovered by 38.172.160.0/19 | 672 100% |
| 38.172.169.0/24 | Valid | Nonecovered by 38.172.160.0/19 | 672 100% |
| 38.172.170.0/24 | Valid | Nonecovered by 38.172.160.0/19 | 672 100% |
| 38.172.171.0/24 | Valid | Nonecovered by 38.172.160.0/19 | 672 100% |
| 38.172.176.0/24 | Valid | Nonecovered by 38.172.160.0/19 | 672 100% |
| 38.172.177.0/24 | Valid | Nonecovered by 38.172.160.0/19 | 672 100% |
| 38.172.178.0/24 | Valid | Nonecovered by 38.172.160.0/19 | 672 100% |
| 38.172.179.0/24 | Valid | Nonecovered by 38.172.160.0/19 | 672 100% |
| 181.41.153.0/24 | Valid | None | 672 100% |
| 38.172.160.0/22 | Valid | Nonecovered by 38.172.160.0/19 | 671 100% |
| 38.172.160.0/24 | Valid | Nonecovered by 38.172.160.0/19 | 671 100% |
| 38.172.161.0/24 | Valid | Nonecovered by 38.172.160.0/19 | 671 100% |
| 38.172.162.0/24 | Valid | Nonecovered by 38.172.160.0/19 | 671 100% |
| 38.172.163.0/24 | Valid | Nonecovered by 38.172.160.0/19 | 671 100% |
| 38.172.180.0/22 | Valid | Nonecovered by 38.172.160.0/19 | 671 100% |
| 38.172.180.0/24 | Valid | Nonecovered by 38.172.160.0/19 | 671 100% |
| 38.172.181.0/24 | Valid | Nonecovered by 38.172.160.0/19 | 671 100% |
| 38.172.182.0/24 | Valid | Nonecovered by 38.172.160.0/19 | 671 100% |
| 38.172.183.0/24 | Valid | Nonecovered by 38.172.160.0/19 | 671 100% |
| 38.172.188.0/24 | Valid | Nonecovered by 38.172.160.0/19 | 670 100% |
| 38.172.189.0/24 | Valid | Nonecovered by 38.172.160.0/19 | 670 100% |
| 38.172.184.0/24 | Valid | Nonecovered by 38.172.160.0/19 | 669 99% |
| 2803:f9e0:1000::/36 | Valid | Nonecovered by 2803:f9e0::/32 | 635 100% |
| 2803:f9e0:3000::/36 | Valid | Nonecovered by 2803:f9e0::/32 | 634 100% |
| 2803:f9e0:b000::/36 | Valid | Nonecovered by 2803:f9e0::/32 | 634 100% |
| 2803:f9e0:e000::/36 | Valid | Nonecovered by 2803:f9e0::/32 | 634 100% |
| 2803:f9e0:f000::/36 | Valid | Nonecovered by 2803:f9e0::/32 | 634 100% |
| 2803:f9e0:2000::/36 | Valid | Nonecovered by 2803:f9e0::/32 | 632 99% |
| 189.127.167.0/24 | Valid | Other IRR onlyRADB | 673 100% |
| 189.127.166.0/24 | Valid | Other IRR onlyRADB | 672 100% |
| 181.41.152.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 189.127.166.0/23 | Valid | RIR databaseLACNIC, RADB | 671 100% |
| 141.136.56.0/24 | Valid | RIR databaseRIPE | 1 0%low visibility |
AS-SET
PeeringDB's irr_as_set for AS270026: AS-SERVITEL. 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 (AS270026 isn't in the set, or no route object for AS270026 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 | AS270026 in it | Not covered | |
|---|---|---|---|---|---|---|
| AS-SERVITEL | In no IRR database read today. | |||||
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 45 are in fix.csv.
- Route object: none35
- Route object: RIR2
- AS-SET: not found1
- Route object: not announced7
| Change | Prefix or set | Detail |
|---|---|---|
| Route object: none | 38.172.164.0/22 | No route object for it. A route object for 38.172.160.0/19 with origin AS270026 covers it (filters allowing more-specifics accept it). Add a route object with origin AS270026 in the RIR database for the space. |
| Route object: none | 38.172.168.0/22 | No route object for it. A route object for 38.172.160.0/19 with origin AS270026 covers it (filters allowing more-specifics accept it). Add a route object with origin AS270026 in the RIR database for the space. |
| Route object: none | 38.172.172.0/22 | No route object for it. A route object for 38.172.160.0/19 with origin AS270026 covers it (filters allowing more-specifics accept it). Add a route object with origin AS270026 in the RIR database for the space. |
| Route object: none | 38.172.164.0/24 | No route object for it. A route object for 38.172.160.0/19 with origin AS270026 covers it (filters allowing more-specifics accept it). Add a route object with origin AS270026 in the RIR database for the space. |
| Route object: none | 38.172.165.0/24 | No route object for it. A route object for 38.172.160.0/19 with origin AS270026 covers it (filters allowing more-specifics accept it). Add a route object with origin AS270026 in the RIR database for the space. |
| Route object: none | 38.172.166.0/24 | No route object for it. A route object for 38.172.160.0/19 with origin AS270026 covers it (filters allowing more-specifics accept it). Add a route object with origin AS270026 in the RIR database for the space. |
| Route object: none | 38.172.167.0/24 | No route object for it. A route object for 38.172.160.0/19 with origin AS270026 covers it (filters allowing more-specifics accept it). Add a route object with origin AS270026 in the RIR database for the space. |
| Route object: none | 38.172.168.0/24 | No route object for it. A route object for 38.172.160.0/19 with origin AS270026 covers it (filters allowing more-specifics accept it). Add a route object with origin AS270026 in the RIR database for the space. |
| Route object: none | 38.172.169.0/24 | No route object for it. A route object for 38.172.160.0/19 with origin AS270026 covers it (filters allowing more-specifics accept it). Add a route object with origin AS270026 in the RIR database for the space. |
| Route object: none | 38.172.170.0/24 | No route object for it. A route object for 38.172.160.0/19 with origin AS270026 covers it (filters allowing more-specifics accept it). Add a route object with origin AS270026 in the RIR database for the space. |
| Route object: none | 38.172.171.0/24 | No route object for it. A route object for 38.172.160.0/19 with origin AS270026 covers it (filters allowing more-specifics accept it). Add a route object with origin AS270026 in the RIR database for the space. |
| Route object: none | 38.172.176.0/24 | No route object for it. A route object for 38.172.160.0/19 with origin AS270026 covers it (filters allowing more-specifics accept it). Add a route object with origin AS270026 in the RIR database for the space. |
| Route object: none | 38.172.177.0/24 | No route object for it. A route object for 38.172.160.0/19 with origin AS270026 covers it (filters allowing more-specifics accept it). Add a route object with origin AS270026 in the RIR database for the space. |
| Route object: none | 38.172.178.0/24 | No route object for it. A route object for 38.172.160.0/19 with origin AS270026 covers it (filters allowing more-specifics accept it). Add a route object with origin AS270026 in the RIR database for the space. |
| Route object: none | 38.172.179.0/24 | No route object for it. A route object for 38.172.160.0/19 with origin AS270026 covers it (filters allowing more-specifics accept it). Add a route object with origin AS270026 in the RIR database for the space. |
| Route object: none | 181.41.153.0/24 | No route object for it. Add a route object with origin AS270026 in the RIR database for the space. |
| Route object: none | 38.172.160.0/22 | No route object for it. A route object for 38.172.160.0/19 with origin AS270026 covers it (filters allowing more-specifics accept it). Add a route object with origin AS270026 in the RIR database for the space. |
| Route object: none | 38.172.160.0/24 | No route object for it. A route object for 38.172.160.0/19 with origin AS270026 covers it (filters allowing more-specifics accept it). Add a route object with origin AS270026 in the RIR database for the space. |
| Route object: none | 38.172.161.0/24 | No route object for it. A route object for 38.172.160.0/19 with origin AS270026 covers it (filters allowing more-specifics accept it). Add a route object with origin AS270026 in the RIR database for the space. |
| Route object: none | 38.172.162.0/24 | No route object for it. A route object for 38.172.160.0/19 with origin AS270026 covers it (filters allowing more-specifics accept it). Add a route object with origin AS270026 in the RIR database for the space. |
| Route object: none | 38.172.163.0/24 | No route object for it. A route object for 38.172.160.0/19 with origin AS270026 covers it (filters allowing more-specifics accept it). Add a route object with origin AS270026 in the RIR database for the space. |
| Route object: none | 38.172.180.0/22 | No route object for it. A route object for 38.172.160.0/19 with origin AS270026 covers it (filters allowing more-specifics accept it). Add a route object with origin AS270026 in the RIR database for the space. |
| Route object: none | 38.172.180.0/24 | No route object for it. A route object for 38.172.160.0/19 with origin AS270026 covers it (filters allowing more-specifics accept it). Add a route object with origin AS270026 in the RIR database for the space. |
| Route object: none | 38.172.181.0/24 | No route object for it. A route object for 38.172.160.0/19 with origin AS270026 covers it (filters allowing more-specifics accept it). Add a route object with origin AS270026 in the RIR database for the space. |
| Route object: none | 38.172.182.0/24 | No route object for it. A route object for 38.172.160.0/19 with origin AS270026 covers it (filters allowing more-specifics accept it). Add a route object with origin AS270026 in the RIR database for the space. |
| Route object: none | 38.172.183.0/24 | No route object for it. A route object for 38.172.160.0/19 with origin AS270026 covers it (filters allowing more-specifics accept it). Add a route object with origin AS270026 in the RIR database for the space. |
| Route object: none | 38.172.188.0/24 | No route object for it. A route object for 38.172.160.0/19 with origin AS270026 covers it (filters allowing more-specifics accept it). Add a route object with origin AS270026 in the RIR database for the space. |
| Route object: none | 38.172.189.0/24 | No route object for it. A route object for 38.172.160.0/19 with origin AS270026 covers it (filters allowing more-specifics accept it). Add a route object with origin AS270026 in the RIR database for the space. |
| Route object: none | 38.172.184.0/24 | No route object for it. A route object for 38.172.160.0/19 with origin AS270026 covers it (filters allowing more-specifics accept it). Add a route object with origin AS270026 in the RIR database for the space. |
| Route object: none | 2803:f9e0:1000::/36 | No route object for it. A route object for 2803:f9e0::/32 with origin AS270026 covers it (filters allowing more-specifics accept it). Add a route object with origin AS270026 in the RIR database for the space. |
| Route object: none | 2803:f9e0:3000::/36 | No route object for it. A route object for 2803:f9e0::/32 with origin AS270026 covers it (filters allowing more-specifics accept it). Add a route object with origin AS270026 in the RIR database for the space. |
| Route object: none | 2803:f9e0:b000::/36 | No route object for it. A route object for 2803:f9e0::/32 with origin AS270026 covers it (filters allowing more-specifics accept it). Add a route object with origin AS270026 in the RIR database for the space. |
| Route object: none | 2803:f9e0:e000::/36 | No route object for it. A route object for 2803:f9e0::/32 with origin AS270026 covers it (filters allowing more-specifics accept it). Add a route object with origin AS270026 in the RIR database for the space. |
| Route object: none | 2803:f9e0:f000::/36 | No route object for it. A route object for 2803:f9e0::/32 with origin AS270026 covers it (filters allowing more-specifics accept it). Add a route object with origin AS270026 in the RIR database for the space. |
| Route object: none | 2803:f9e0:2000::/36 | No route object for it. A route object for 2803:f9e0::/32 with origin AS270026 covers it (filters allowing more-specifics accept it). Add a route object with origin AS270026 in the RIR database for the space. |
| Route object: RIR | 189.127.167.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 189.127.166.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| AS-SET: not found | AS-SERVITEL | PeeringDB names AS-SERVITEL; no IRR database read has it. |
Route objects not announced
Route objects with origin AS270026 whose prefix no peer sees AS270026 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 38.172.160.0/19 | ARIN, RADB | Valid |
| 141.136.56.0/23 | RADB, RIPE | Valid |
| 141.136.57.0/24 | RIPE | Valid |
| 154.12.112.0/24 | RADB | No ROA |
| 154.12.113.0/24 | RADB | No ROA |
| 181.41.155.0/24 | RIPE | Valid |
| 2803:f9e0::/32 | LACNIC, 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.