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.
Checking routing, RPKI, reverse DNS, blocklists and the registry. This usually takes 3 to 10 seconds.
Problem: AS200154 (IZONE-AS IZONE LLC) announces 12 IPv4 and 4 IPv6 prefixes. 1 problem · 1 warning
| AS page | AS200154 |
|---|---|
| Holder | IZONE-AS IZONE LLC |
| Allocation | RIPE NCC, Azerbaijan (AZ), allocated 2013-09-23 |
| Prefixes (IPv4 / IPv6) | 12 / 4 |
| RPKI valid | 94% (15 / 16) |
| Upstreams and peers | 3 |
| Peering policy | Open |
What to fix
-
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.
-
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.
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.
| Holder | IZONE-AS IZONE LLC |
|---|---|
| IPv4 prefixes | 12 |
| IPv6 prefixes | 4 |
| RPKI | 15 valid · 1 invalid |
| Downstream networks | 12 |
| Prefix | RPKI |
|---|---|
| 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 lookupRegistration Found at rdap.db.ripe.net.
- Pass: Found at rdap.db.ripe.net.
| Name | IZONE-AS |
|---|---|
| Handle | AS200154 |
| Range | AS200154 |
| Status | active |
| Registered | 2013-09-23T13:36:30Z |
| Last changed | 2026-10-21T06:31:34Z |
| Abuse contact | azad.dursunov@bossnet.az |
| Registry (RIR) | RIPE NCC |
|---|---|
| Country | Azerbaijan (AZ) |
| Delegated on | 2013-09-23 |
| Status | Allocated |
| Delegated range | AS200154 |
Source: RIR delegation data, updated daily. The country is where the range was registered, not necessarily where it is used.
| Role | Name | |
|---|---|---|
| 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 lookupPeeringDB 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.
| Network | IZONE LLC (BEEONLINE) |
|---|---|
| AS number | AS200154 |
| Type | Cable/DSL/ISP, Regional |
| Website | https://izone.az |
| Prefixes (IPv4 / IPv6) | 8 / 2 |
| Traffic | 50-100Gbps, Balanced |
| Peering policy | Open |
| Locations | Not Required |
| Ratio required | No |
| Contracts | Not Required |
| Last updated | 2026-01-01 |
| Technical | farid@izone.az |
|---|---|
| Public Relations | azad.dursunov@izone.az |
Source: PeeringDB. Results are cached for an hour.
Open in PeeringDB lookup