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

AS200154 ·

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

Problem: AS200154 (IZONE-AS IZONE LLC) announces 12 IPv4 and 4 IPv6 prefixes. 1 problem · 1 warning

AS pageAS200154
HolderIZONE-AS IZONE LLC
AllocationRIPE NCC, Azerbaijan (AZ), allocated 2013-09-23
Prefixes (IPv4 / IPv6)12 / 4
RPKI valid94% (15 / 16)
Upstreams and peers3
Peering policyOpen

What to fix

  1. Problem

    1 of 16 announced prefixes are RPKI invalid: 2a00:c0a0:8000::/34.

    A ROA covers them but does not allow this origin or prefix length, so networks that filter (most large ones do) drop these routes.

    Fix: Fix the ROAs (origin AS and max length) at your RIR, or stop announcing the routes.

    Open in RPKI / ROA validator Guide

  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

Checks

Routing and RPKI 1 of 16 announced prefixes are RPKI invalid: 2a00:c0a0:8000::/34.
  • Pass: AS200154 announces 12 IPv4 and 4 IPv6 prefixes.
  • Problem: 1 of 16 announced prefixes are RPKI invalid: 2a00:c0a0:8000::/34.
  • Info: 15 of 16 announced prefixes are RPKI valid.
  • Pass: Every announced prefix has an IRR route object.
  • Info: 3 upstreams and peers, 12 downstream networks seen.
HolderIZONE-AS IZONE LLC
IPv4 prefixes12
IPv6 prefixes4
RPKI15 valid · 1 invalid
Downstream networks12
Routes to fix
PrefixRPKI
2a00:c0a0:8000::/34 RPKI invalid

Upstreams and peers seen to the left 3

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.
NameIZONE-AS
HandleAS200154
RangeAS200154
Statusactive
Registered2013-09-23T13:36:30Z
Last changed2026-10-21T06:31:34Z
Abuse contactazad.dursunov@bossnet.az
Allocation
Registry (RIR)RIPE NCC
CountryAzerbaijan (AZ)
Delegated on2013-09-23
StatusAllocated
Delegated rangeAS200154

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

Contacts
RoleNameEmail
registrant BEEONLINE-MNT
registrant IZONE LLC
registrant RIPE-NCC-END-MNT
abuse Technical Department azad.dursunov@bossnet.az

Source: https://rdap.db.ripe.net/autnum/200154. 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: AS200154 is in PeeringDB as IZONE LLC.
  • Info: Peering policy: Open.
  • Info: No internet exchange ports are listed.
  • Warning: No IRR as-set is listed.
NetworkIZONE LLC (BEEONLINE)
AS numberAS200154
TypeCable/DSL/ISP, Regional
Websitehttps://izone.az
Prefixes (IPv4 / IPv6)8 / 2
Traffic50-100Gbps, Balanced
Peering policyOpen
LocationsNot Required
Ratio requiredNo
ContractsNot Required
Last updated2026-01-01
Contacts
Technicalfarid@izone.az
Public Relationsazad.dursunov@izone.az

Source: PeeringDB. Results are cached for an hour.

Open in PeeringDB lookup