Network · data from 2026-11-12
AS269836 AS269836 - TERABYTE COMUNICACIONES S.A.S
Registry name: AS269836 - TERABYTE COMUNICACIONES S.A.S, CO · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS269836, 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.
| 2803:7c60:1000::/36 | Valid | Other IRR onlyRADB | 634 100% |
| 2803:7c60:2000::/36 | Valid | Other IRR onlyRADB | 634 100% |
| 45.176.70.0/23 | Valid | RIR databaseLACNIC, RADB | 670 100% |
| 45.176.193.0/24 | Valid | RIR databaseLACNIC, RADB | 670 100% |
| 45.176.71.0/24 | Valid | RIR databaseLACNIC | 669 99% |
AS-SET
AS269836 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 8 are in fix.csv.
- Route object: RIR2
- Route object: not announced6
| Change | Prefix or set | Detail |
|---|---|---|
| Route object: RIR | 2803:7c60:1000::/36 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 2803:7c60:2000::/36 | Route object only in RADB. Add it in the RIR database for the space. |
Route objects not announced
Route objects with origin AS269836 whose prefix no peer sees AS269836 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 45.176.70.0/24 | LACNIC | Valid |
| 190.107.20.80/28 | LACNIC | Valid |
| 2800:490:c800:1100::/56 | LACNIC | Valid |
| 2800:490:e000:b100::/56 | LACNIC | Valid |
| 2800:490:e000:f200::/56 | LACNIC | Valid |
| 2803:7c60::/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.