ITELKOM
AS262215 is ITELKOM (itelkom.co). It announces 10,752 IPv4 addresses in 39 prefixes, and 3 IPv6 prefixes.
Colombia· LACNIC· allocated 2012-02-01· isp
Where its space is
The IPv4 it announces that IP Geolocation places, by country. A /24 counts for the AS announcing most of it.
- Colombia216 · 100.00%
Registry record
Its ASN Whois record, as the registry publishes it.
- name
- ITELKOM
- org
- CO-INSA10-LACNIC
- org name
- ITELKOM
- org address
- No. 95-35 OF. 409, Avenida Carrera 19, Bogota, 123, CO
- org country
- CO
- country
- CO
- source
- lacnic
- status
- DIRECT ALLOCATION
- created
- 2012-02-01
- updated
- 2023-08-08
- descr
- ITELKOM
- abuse
- LMP25
- abuse name
- Andres Felipe Heras Urruchurtu
- abuse email
- andres.heras@itelkom.co
- abuse phone
- +57 3007724633#0000
- abuse kind
- role
- admin
- LMP25
- admin name
- Andres Felipe Heras Urruchurtu
- admin email
- andres.heras@itelkom.co
- admin phone
- +57 3007724633#0000
- admin kind
- role
- tech
- LMP25
- tech name
- Andres Felipe Heras Urruchurtu
- tech email
- andres.heras@itelkom.co
- tech phone
- +57 3007724633#0000
- tech kind
- role
What the databases see
Addresses each address-keyed database holds in the IPv4 it announces, as a share of that space, with its largest providers. Counts overlap.
- VPN IP573best_proxy_switcher5.33%
- novada, dataimpulse, geonode1.67%
- None here
- floppydata0.01%
- None here
- None here
- Hosting IP9,21685.71%
- None here
- None here
- None here
- SSH IP810.75%
- SMTP IP2582.40%
- 0.37%
IPv4 prefixes
Every IPv4 prefix BGP Route saw it announce. A prefix another AS also announces says so.
| PREFIX | COUNTRY | RPKI | PEERS | FIRST SEEN |
|---|---|---|---|---|
| 179.60.240.0/24 | — | valid | 17 | 2026-10-02 |
| 179.60.241.0/24 | — | valid | 17 | 2026-10-02 |
| 179.60.242.0/24 | — | valid | 17 | 2026-10-02 |
| 179.60.243.0/24 | — | valid | 17 | 2026-10-02 |
| 186.159.112.0/24 | — | valid | 17 | 2026-10-02 |
| 186.159.113.0/24 | — | valid | 17 | 2026-10-02 |
| 186.159.114.0/24 | — | valid | 17 | 2026-10-02 |
| 186.159.115.0/24 | Colombia | valid | 17 | 2026-10-02 |
| 201.131.188.0/22 | — | not found | 17 | 2026-10-02 |
| 201.219.193.0/24 | — | valid | 17 | 2026-10-02 |
| 201.219.194.0/24 | — | valid | 17 | 2026-10-02 |
| 201.219.196.0/24 | — | valid | 17 | 2026-10-02 |
| 201.219.197.0/24 | — | valid | 17 | 2026-10-02 |
| 201.219.198.0/24 | — | valid | 17 | 2026-10-02 |
| 201.219.199.0/24 | — | valid | 17 | 2026-10-02 |
| 201.219.200.0/24 | — | valid | 17 | 2026-10-02 |
| 201.219.201.0/24 | — | valid | 17 | 2026-10-02 |
| 201.219.202.0/24 | — | valid | 17 | 2026-10-02 |
| 201.219.203.0/24 | — | valid | 17 | 2026-10-02 |
| 201.219.204.0/24 | — | valid | 17 | 2026-10-02 |
| 201.219.205.0/24 | — | valid | 17 | 2026-10-02 |
| 201.219.206.0/24 | — | valid | 17 | 2026-10-02 |
| 201.219.207.0/24 | — | valid | 17 | 2026-10-02 |
| 201.219.208.0/24 | — | valid | 17 | 2026-10-02 |
| 201.219.209.0/24 | — | valid | 17 | 2026-10-02 |
| 201.219.210.0/24 | — | valid | 17 | 2026-10-02 |
| 201.219.211.0/24 | — | valid | 17 | 2026-10-02 |
| 201.219.212.0/24 | — | valid | 17 | 2026-10-02 |
| 201.219.213.0/24 | — | valid | 17 | 2026-10-02 |
| 201.219.214.0/24 | — | valid | 17 | 2026-10-02 |
| 201.219.215.0/24 | — | valid | 17 | 2026-10-02 |
| 201.219.216.0/24 | — | valid | 17 | 2026-10-02 |
| 201.219.217.0/24 | — | valid | 17 | 2026-10-02 |
| 201.219.218.0/24 | — | valid | 17 | 2026-10-02 |
| 201.219.219.0/24 | — | valid | 17 | 2026-10-02 |
| 201.219.220.0/24 | — | valid | 17 | 2026-10-02 |
| 201.219.221.0/24 | — | valid | 17 | 2026-10-02 |
| 201.219.222.0/24 | — | valid | 17 | 2026-10-02 |
| 201.219.223.0/24 | — | valid | 17 | 2026-10-02 |
IPv6 prefixes
Every IPv6 prefix BGP Route saw it announce.
Test the real build first.
An evaluation license puts a full current build in your hands — every row, every column, no sampling — so you can measure it against your own traffic before anyone talks about terms.