bgpreport

Network · data from 2026-11-12

AS213438 colocatel-inc

Registry name: colocatel-inc ColocaTel Inc., SC · PeeringDB

19IPv4 routes 100.0% RPKI valid · 94.7% with a route object
22IPv6 routes 90.9% RPKI valid · 90.9% with a route object
1RPKI invalid 1 origin · 0 maxLength
1No ROA 3 with no route object for this origin
2Low visibility seen by under 10% of full-table peers
1Route objects not announced registered with origin AS213438, seen from no peer

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 2
2a06:a001:a010::/44 No ROA None 633 100% 67
37.60.141.0/24 Valid None 670 100% 66
31.56.110.0/24 Valid RIR databaseRADB, RIPE 671 100% 66
31.58.249.0/24 Valid RIR databaseRIPE 671 100% 66
45.129.230.0/23 Valid RIR databaseAPNIC 671 100% 66
50.118.225.0/24 Valid RIR databaseARIN, RADB 671 100% 66
78.142.18.0/24 Valid RIR databaseRIPE 671 100% 66
79.124.8.0/24 Valid RIR databaseRIPE 671 100% 66
185.196.220.0/24 Valid RIR databaseRIPE 671 100% 66
217.60.79.0/24 Valid RIR databaseRIPE 671 100% 66
5.253.84.0/24 Valid RIR databaseRIPE 670 100% 66
5.253.86.0/24 Valid RIR databaseRIPE 670 100% 66
45.134.225.0/24 Valid RIR databaseRIPE 670 100% 66
78.159.130.0/24 Valid RIR databaseRIPE 669 99% 68
193.142.147.0/24 Valid RIR databaseRIPE 666 99% 66
94.26.105.0/24 Valid RIR databaseRIPE 665 99% 66
192.109.138.0/24 Valid RIR databaseRIPE 665 99% 66
193.142.146.0/24 Valid RIR databaseRIPE 665 99% 66
93.152.219.0/24 Valid RIR databaseRIPE 662 98% 66
2a0f:ca80:f000::/40 Valid RIR databaseRIPE 633 100% 69
2a0f:ca80::/48 Valid RIR databaseRIPE 631 99% 67
2a0f:ca80:1::/48 Valid RIR databaseRIPE 631 99% 67
2a0f:ca80:616::/48 Valid RIR databaseRIPE 631 99% 67
2a0f:ca80:617::/48 Valid RIR databaseRIPE 631 99% 67
2a0f:ca80:619::/48 Valid RIR databaseRIPE 631 99% 67
2a0f:ca80:666::/48 Valid RIR databaseRIPE 631 99% 67
2a0f:ca80:fe0::/44 Valid RIR databaseRIPE 631 99% 67
2a0f:ca80:1100::/40 Valid RIR databaseRIPE 631 99% 67
2a0f:ca80:1337::/48 Valid RIR databaseRIPE 631 99% 67
2a0f:ca80:1338::/48 Valid RIR databaseRIPE 631 99% 67
2a0f:ca80:abcd::/48 Valid RIR databaseRIPE 631 99% 67
2a0f:ca83:1234::/48 Valid RIR databaseRIPE 631 99% 67
2a0f:ca83:1337::/48 Valid RIR databaseRIPE 631 99% 67
2a0f:ca84::/40 Valid RIR databaseRIPE 631 99% 67
2a0f:ca86::/40 Valid RIR databaseRIPE 631 99% 67
2a0f:ca80:beef::/48 Valid RIR databaseRIPE 630 99% 67
2a0f:ca80:deed::/48 Valid RIR databaseRIPE 630 99% 67
2a0f:ca81:deed::/48 Valid RIR databaseRIPE 628 99% 67
2a13:29c0::/29 Valid RIR databaseRIPE 628 99% 67
205.234.121.0/24 Valid RIR databaseRIPE 1 0%low visibility 1

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
ChangePrefix or setDetailFull-table peers
ROA: origin2a0f:ca81:b00b::/48ROAs covering it name AS215762, not AS213438. If AS213438 should announce it, add a ROA for AS213438.2 of 636
Route object: none2a0f:ca81:b00b::/48Route objects for it name AS215762. Add a route object with origin AS213438 in the RIR database for the space.2 of 636
ROA: none2a06:a001:a010::/44No ROA covers it. Add a ROA for AS213438, maxLength 44.633 of 636
Route object: none2a06:a001:a010::/44No route object for it. Add a route object with origin AS213438 in the RIR database for the space.633 of 636
Route object: none37.60.141.0/24No route object for it. Add a route object with origin AS213438 in the RIR database for the space.670 of 673

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/24RIPEValid

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.