Network · data from 2026-11-12
AS265624 AS265624 - TELTAN TELECOMUNICACIONES, S. DE R.L. DE C.V.
Registry name: AS265624 - TELTAN TELECOMUNICACIONES, S. DE R.L. DE C.V., MX · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS265624, 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.4.48.0/24 | Valid | Nonecovered by 38.4.48.0/21 | 672 100% |
| 200.108.184.0/24 | Valid | Nonecovered by 200.108.184.0/22 | 670 100% |
| 2806:3a5:1000::/36 | Valid | Nonecovered by 2806:3a5::/32 | 636 100% |
| 38.4.50.0/24 | Valid | Nonecovered by 38.4.48.0/21 | 50 7%low visibility |
| 38.4.49.0/24 | Valid | Nonecovered by 38.4.48.0/21 | 3 0%low visibility |
| 2806:3a5::/36 | Valid | Nonecovered by 2806:3a5::/32 | 2 0%low visibility |
| 200.108.186.0/24 | Valid | Other IRR onlyRADB | 672 100% |
| 200.108.187.0/24 | Valid | Other IRR onlyRADB | 672 100% |
| 200.108.185.0/24 | Valid | Other IRR onlyRADB | 3 0%low visibility |
AS-SET
AS265624 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 12 are in fix.csv.
- Route object: none6
- Route object: RIR3
- Route object: not announced3
| Change | Prefix or set | Detail |
|---|---|---|
| Route object: none | 38.4.48.0/24 | No route object for it. A route object for 38.4.48.0/21 with origin AS265624 covers it (filters allowing more-specifics accept it). Add a route object with origin AS265624 in the RIR database for the space. |
| Route object: none | 200.108.184.0/24 | No route object for it. A route object for 200.108.184.0/22 with origin AS265624 covers it (filters allowing more-specifics accept it). Add a route object with origin AS265624 in the RIR database for the space. |
| Route object: none | 2806:3a5:1000::/36 | No route object for it. A route object for 2806:3a5::/32 with origin AS265624 covers it (filters allowing more-specifics accept it). Add a route object with origin AS265624 in the RIR database for the space. |
| Route object: none | 38.4.50.0/24 | No route object for it. A route object for 38.4.48.0/21 with origin AS265624 covers it (filters allowing more-specifics accept it). Add a route object with origin AS265624 in the RIR database for the space. |
| Route object: none | 38.4.49.0/24 | No route object for it. A route object for 38.4.48.0/21 with origin AS265624 covers it (filters allowing more-specifics accept it). Add a route object with origin AS265624 in the RIR database for the space. |
| Route object: none | 2806:3a5::/36 | No route object for it. A route object for 2806:3a5::/32 with origin AS265624 covers it (filters allowing more-specifics accept it). Add a route object with origin AS265624 in the RIR database for the space. |
| Route object: RIR | 200.108.186.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 200.108.187.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 200.108.185.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
Route objects not announced
Route objects with origin AS265624 whose prefix no peer sees AS265624 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 38.4.48.0/21 | ARIN, RADB | Valid |
| 200.108.184.0/22 | LACNIC, RADB | Valid |
| 2806:3a5::/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.