Skip to content
thenetworkery

Network report

Who holds an IP address, prefix or AS number, how it is routed (origin AS, RPKI, IRR), its reverse DNS, blocklist listings and PeeringDB record, with what to fix first.

IP address, prefix or AS number

AS26611 · 

curl -s "https://thenetworkery.com/api/v1/network-report?query=AS26611"
JSON Docs

Warning: AS26611 (AS26611) announces 255 IPv4 and 1194 IPv6 prefixes. 3 warnings

AS pageAS26611
HolderAS26611 - COMUNICACION CELULAR S.A. COMCEL S.A.
AllocationLACNIC, Colombia (CO), allocated 2002-11-01
Prefixes (IPv4 / IPv6)255 / 1194
RPKI valid97% (1403 / 1449)
Upstreams and peers1

What to fix

  1. Warning

    10 of 1449 announced prefixes have no ROA (RPKI not found): 166.210.0.0/17, 166.210.32.0/24, 166.210.38.0/24, 166.210.128.0/18, 166.210.224.0/20 (+5).

    Without a ROA, networks cannot tell your routes from a hijack.

    Fix: Create a ROA for each at your RIR portal, with origin AS26611 and a max length equal to the prefix length:

    166.210.0.0/17 AS26611 max-length /17
166.210.32.0/24 AS26611 max-length /24
166.210.38.0/24 AS26611 max-length /24
166.210.128.0/18 AS26611 max-length /18
166.210.224.0/20 AS26611 max-length /20
166.210.224.0/24 AS26611 max-length /24
166.210.225.0/24 AS26611 max-length /24
166.210.227.0/24 AS26611 max-length /24
166.238.0.0/16 AS26611 max-length /16
166.238.240.0/20 AS26611 max-length /20

    Open in RPKI / ROA validator Guide

  2. Warning

    1426 of 1449 announced prefixes have no IRR route object: 2800:800:d4c::/47, 2800:800:e5e::/47, 2800:800:c90::/46, 181.245.128.0/17, 2800:800:ce4::/46 (+1421).

    Many networks build their prefix filters from IRR data; without route objects some of them drop the routes.

    Fix: Create route (IPv4) and route6 (IPv6) objects with origin AS26611 in your RIR’s IRR database (or RADB).

    route6: 2800:800:d4c::/47
origin: AS26611

route6: 2800:800:e5e::/47
origin: AS26611

route6: 2800:800:c90::/46
origin: AS26611

    Open in ASN & BGP prefix lookup

  3. Warning

    PeeringDB did not answer: HTTP 404

    Fix: Try again in a minute.

    Open in PeeringDB lookup

Checks

Routing and RPKI 10 of 1449 announced prefixes have no ROA (RPKI not found): 166.210.0.0/17, 166.210.32.0/24, 166.210.38.0/24, 166.210.128.0/18, 166.210.224.0/20 (+5).
  • Pass: AS26611 announces 255 IPv4 and 1194 IPv6 prefixes.
  • Warning: 10 of 1449 announced prefixes have no ROA (RPKI not found): 166.210.0.0/17, 166.210.32.0/24, 166.210.38.0/24, 166.210.128.0/18, 166.210.224.0/20 (+5).
  • Info: 1403 of 1449 announced prefixes are RPKI valid.
  • Info: The RPKI state of 36 prefixes was not looked up (no ROA of AS26611 covers them; only the first 10 are checked).
  • Warning: 1426 of 1449 announced prefixes have no IRR route object: 2800:800:d4c::/47, 2800:800:e5e::/47, 2800:800:c90::/46, 181.245.128.0/17, 2800:800:ce4::/46 (+1421).
  • Info: One upstream or peer seen (AS14080): an outage there takes the whole network off the internet.
HolderAS26611 - COMUNICACION CELULAR S.A. COMCEL S.A.
IPv4 prefixes255
IPv6 prefixes1194
RPKI1403 valid · 10 not found · 36 not looked up
Without IRR route object1426
Downstream networks1
Routes to fix
PrefixRPKI
166.210.0.0/17 No ROA
166.210.32.0/24 No ROA
166.210.38.0/24 No ROA
166.210.128.0/18 No ROA
166.210.224.0/20 No ROA
166.210.224.0/24 No ROA
166.210.225.0/24 No ROA
166.210.227.0/24 No ROA
166.238.0.0/16 No ROA
166.238.240.0/20 No ROA

Upstreams and peers seen to the left 1

AS14080 Telmex Colombia

Announced prefixes 1449

166.210.0.0/17 166.210.32.0/24 166.210.38.0/24 166.210.128.0/18 166.210.224.0/20 166.210.224.0/24 166.210.225.0/24 166.210.227.0/24 166.238.0.0/16 166.238.240.0/20 181.144.0.0/17 181.144.128.0/17 181.145.0.0/17 181.145.128.0/17 181.146.0.0/17 181.146.128.0/17 181.147.0.0/17 181.147.128.0/17 181.148.0.0/17 181.148.128.0/17 181.149.0.0/17 181.149.128.0/17 181.150.0.0/17 181.150.128.0/17 181.151.0.0/16 181.152.0.0/17 181.152.128.0/17 181.153.0.0/17 181.153.128.0/17 181.154.0.0/17 181.154.128.0/17 181.155.0.0/17 181.155.128.0/17 181.156.0.0/17 181.156.128.0/17 181.157.0.0/17 181.157.128.0/17 181.158.0.0/17 181.158.128.0/17 181.159.0.0/17 181.159.128.0/17 181.240.0.0/17 181.240.128.0/17 181.241.0.0/16 181.242.0.0/17 181.242.128.0/17 181.243.0.0/17 181.243.128.0/17 181.244.0.0/17 181.244.128.0/17 181.245.0.0/17 181.245.128.0/17 181.246.0.0/16 181.247.0.0/17 181.247.128.0/17 181.248.0.0/16 181.249.0.0/17 181.249.128.0/17 181.250.0.0/17 181.250.128.0/17 181.251.0.0/17 181.251.128.0/17 181.252.0.0/17 181.252.128.0/17 181.253.0.0/16 181.254.0.0/17 181.254.128.0/17 181.255.0.0/17 181.255.128.0/17 190.125.0.0/17 190.125.128.0/17 190.126.0.0/17 190.126.128.0/17 190.127.128.0/21 190.127.192.0/24 190.127.193.0/24 190.127.194.0/24 190.127.195.0/24 190.127.208.0/20 190.127.224.0/21 190.127.234.0/24 190.127.237.0/24 190.127.241.0/24 190.127.249.0/24 190.127.251.0/24 190.127.254.0/24 190.127.255.0/24 190.130.72.0/21 190.130.80.0/24 190.130.81.0/24 190.130.82.0/24 190.130.83.0/24 190.130.84.0/24 190.130.85.0/24 190.130.86.0/24 190.130.87.0/24 190.130.88.0/24 190.130.89.0/24 190.130.90.0/24 190.130.91.0/24

Showing the first 100.

Source: RIPEstat (RIPE NCC RIS, Routinator, IRR); AS names: Team Cymru

Open in ASN & BGP prefix lookup
Registration Found at rdap.arin.net.
  • Pass: Found at rdap.arin.net.
Name26611
HandleAS26611
RangeAS26611
Statusactive
Registered2002-11-01T12:00:00Z
Last changed2021-10-25T23:25:04Z
Abuse contactciro.mantilla@claro.com.co
Allocation
Registry (RIR)LACNIC
CountryColombia (CO)
Delegated on2002-11-01
StatusAllocated
Delegated rangeAS26611

Source: RIR delegation data, updated daily. The country is where the range was registered, not necessarily where it is used.

Contacts
RoleNameEmail
registrant COMUNICACIÓN CELULAR S.A. COMCEL S.A.
administrative, technical Ciro Mauricio Mantilla ciro.mantilla@claro.com.co
abuse Network Security Team ciro.mantilla@claro.com.co

Source: https://rdap.arin.net/registry/autnum/26611. Registration data from rdap.arin.net, shown under its terms of use (terms): not for marketing or bulk collection.

Open in WHOIS / RDAP lookup
PeeringDB PeeringDB did not answer: HTTP 404
  • Warning: PeeringDB did not answer: HTTP 404

Source: PeeringDB. Results are cached for an hour.

Open in PeeringDB lookup