Network · data from 2026-11-12
AS213438 colocatel-inc
Registry name: colocatel-inc ColocaTel Inc., SC · PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS213438, 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.
| 2a0f:ca81:b00b::/48 | Invalid: origin | Other origin only | 2 0%low visibility |
| 2a06:a001:a010::/44 | No ROA | None | 633 100% |
| 37.60.141.0/24 | Valid | None | 670 100% |
| 31.56.110.0/24 | Valid | RIR databaseRADB, RIPE | 671 100% |
| 31.58.249.0/24 | Valid | RIR databaseRIPE | 671 100% |
| 45.129.230.0/23 | Valid | RIR databaseAPNIC | 671 100% |
| 50.118.225.0/24 | Valid | RIR databaseARIN, RADB | 671 100% |
| 78.142.18.0/24 | Valid | RIR databaseRIPE | 671 100% |
| 79.124.8.0/24 | Valid | RIR databaseRIPE | 671 100% |
| 185.196.220.0/24 | Valid | RIR databaseRIPE | 671 100% |
| 217.60.79.0/24 | Valid | RIR databaseRIPE | 671 100% |
| 5.253.84.0/24 | Valid | RIR databaseRIPE | 670 100% |
| 5.253.86.0/24 | Valid | RIR databaseRIPE | 670 100% |
| 45.134.225.0/24 | Valid | RIR databaseRIPE | 670 100% |
| 78.159.130.0/24 | Valid | RIR databaseRIPE | 669 99% |
| 193.142.147.0/24 | Valid | RIR databaseRIPE | 666 99% |
| 94.26.105.0/24 | Valid | RIR databaseRIPE | 665 99% |
| 192.109.138.0/24 | Valid | RIR databaseRIPE | 665 99% |
| 193.142.146.0/24 | Valid | RIR databaseRIPE | 665 99% |
| 93.152.219.0/24 | Valid | RIR databaseRIPE | 662 98% |
| 2a0f:ca80:f000::/40 | Valid | RIR databaseRIPE | 633 100% |
| 2a0f:ca80::/48 | Valid | RIR databaseRIPE | 631 99% |
| 2a0f:ca80:1::/48 | Valid | RIR databaseRIPE | 631 99% |
| 2a0f:ca80:616::/48 | Valid | RIR databaseRIPE | 631 99% |
| 2a0f:ca80:617::/48 | Valid | RIR databaseRIPE | 631 99% |
| 2a0f:ca80:619::/48 | Valid | RIR databaseRIPE | 631 99% |
| 2a0f:ca80:666::/48 | Valid | RIR databaseRIPE | 631 99% |
| 2a0f:ca80:fe0::/44 | Valid | RIR databaseRIPE | 631 99% |
| 2a0f:ca80:1100::/40 | Valid | RIR databaseRIPE | 631 99% |
| 2a0f:ca80:1337::/48 | Valid | RIR databaseRIPE | 631 99% |
| 2a0f:ca80:1338::/48 | Valid | RIR databaseRIPE | 631 99% |
| 2a0f:ca80:abcd::/48 | Valid | RIR databaseRIPE | 631 99% |
| 2a0f:ca83:1234::/48 | Valid | RIR databaseRIPE | 631 99% |
| 2a0f:ca83:1337::/48 | Valid | RIR databaseRIPE | 631 99% |
| 2a0f:ca84::/40 | Valid | RIR databaseRIPE | 631 99% |
| 2a0f:ca86::/40 | Valid | RIR databaseRIPE | 631 99% |
| 2a0f:ca80:beef::/48 | Valid | RIR databaseRIPE | 630 99% |
| 2a0f:ca80:deed::/48 | Valid | RIR databaseRIPE | 630 99% |
| 2a0f:ca81:deed::/48 | Valid | RIR databaseRIPE | 628 99% |
| 2a13:29c0::/29 | Valid | RIR databaseRIPE | 628 99% |
| 205.234.121.0/24 | Valid | RIR databaseRIPE | 1 0%low visibility |
AS-SET
AS213438's PeeringDB record names no 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 6 are in fix.csv.
- ROA: origin1
- ROA: none1
- Route object: none3
- Route object: not announced1
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: origin | 2a0f:ca81:b00b::/48 | ROAs covering it name AS215762, not AS213438. If AS213438 should announce it, add a ROA for AS213438. |
| Route object: none | 2a0f:ca81:b00b::/48 | Route objects for it name AS215762. Add a route object with origin AS213438 in the RIR database for the space. |
| ROA: none | 2a06:a001:a010::/44 | No ROA covers it. Add a ROA for AS213438, maxLength 44. |
| Route object: none | 2a06:a001:a010::/44 | No route object for it. Add a route object with origin AS213438 in the RIR database for the space. |
| Route object: none | 37.60.141.0/24 | No route object for it. Add a route object with origin AS213438 in the RIR database for the space. |
Route objects not announced
Route objects with origin AS213438 whose prefix no peer sees AS213438 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 109.236.61.0/24 | RIPE | 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.