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

AS204666 ·

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

Warning: AS204666 (TLAPNET-CZ Jiri Tlapak) announces 38 IPv4 and 11 IPv6 prefixes. 3 warnings

AS pageAS204666
HolderTLAPNET-CZ Jiri Tlapak
AllocationRIPE NCC, Czechia (CZ), allocated 2018-01-29
Prefixes (IPv4 / IPv6)38 / 11
RPKI valid100% (49 / 49)
Upstreams and peers2

What to fix

  1. Warning

    6 of 49 announced prefixes have no IRR route object: 185.87.140.0/22, 185.74.60.0/24, 185.188.100.0/24, 185.64.220.0/24, 185.87.143.0/24 (+1).

    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 AS204666 in your RIR’s IRR database (or RADB).

    route: 185.87.140.0/22
    origin: AS204666
    
    route: 185.74.60.0/24
    origin: AS204666
    
    route: 185.188.100.0/24
    origin: AS204666

    Open in ASN & BGP prefix lookup

  2. Warning

    No IRR as-set is listed.

    Peers and route servers build prefix filters from the as-set. Without one they fall back to the AS number alone, which breaks as soon as you have customers.

    Fix: Create an as-set in your RIR’s IRR database and add it to your PeeringDB record.

    Open in PeeringDB lookup

  3. Warning

    No public NOC, policy or technical contact.

    Other networks use these addresses to set up peering and to reach you during an incident.

    Fix: Add a role contact (for example noc@ or peering@ an address you monitor) with visibility Public.

    Open in PeeringDB lookup

Checks

Routing and RPKI 6 of 49 announced prefixes have no IRR route object: 185.87.140.0/22, 185.74.60.0/24, 185.188.100.0/24, 185.64.220.0/24, 185.87.143.0/24 (+1).
  • Pass: AS204666 announces 38 IPv4 and 11 IPv6 prefixes.
  • Pass: All 49 announced prefixes are RPKI valid.
  • Warning: 6 of 49 announced prefixes have no IRR route object: 185.87.140.0/22, 185.74.60.0/24, 185.188.100.0/24, 185.64.220.0/24, 185.87.143.0/24 (+1).
  • Info: 2 upstreams and peers, 2 downstream networks seen.
HolderTLAPNET-CZ Jiri Tlapak
IPv4 prefixes38
IPv6 prefixes11
RPKI49 valid
Without IRR route object6
Downstream networks2

Upstreams and peers seen to the left 2

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

Open in ASN & BGP prefix lookup
Registration Found at rdap.db.ripe.net.
  • Pass: Found at rdap.db.ripe.net.
NameTLAPNET-CZ
HandleAS204666
RangeAS204666
Statusactive
Registered2018-01-29T15:34:02Z
Last changed2026-08-17T07:34:37Z
Abuse contactzneuziti@tlapnet.cz
Allocation
Registry (RIR)RIPE NCC
CountryCzechia (CZ)
Delegated on2018-01-29
StatusAllocated
Delegated rangeAS204666

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

Contacts
RoleNameEmail
registrant Jiri Tlapak
registrant RIPE-NCC-END-MNT
registrant TLAPNET-MNT
abuse Abuse Contact zneuziti@tlapnet.cz

Source: https://rdap.db.ripe.net/autnum/204666. Registration data from rdap.db.ripe.net, shown under its terms of use (terms): not for marketing or bulk collection. Personal contacts in this registry are not shown.

Open in WHOIS / RDAP lookup
PeeringDB No IRR as-set is listed.
  • Pass: AS204666 is in PeeringDB as Jiri Tlapak.
  • Info: No internet exchange ports are listed.
  • Warning: No IRR as-set is listed.
  • Warning: No public NOC, policy or technical contact.
  • Info: The record was last updated 2023-11-21.
NetworkJiri Tlapak
AS numberAS204666
Type, Not Disclosed
TrafficNot Disclosed
Ratio requiredNo
Last updated2023-11-21

Source: PeeringDB. Results are cached for an hour.

Open in PeeringDB lookup