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

AS204539 ·

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

Warning: AS204539 (AXIC-Axivora-Connect-Ltd Axivora Connec…) announces 1 IPv4 and 14 IPv6 prefixes. 2 warnings

AS pageAS204539
HolderAXIC-Axivora-Connect-Ltd Axivora Connect Ltd
AllocationRIPE NCC, United Kingdom (GB), allocated 2025-10-23
Prefixes (IPv4 / IPv6)1 / 14
RPKI valid73% (11 / 15)
Upstreams and peers25
Peering policyOpen

What to fix

  1. Warning

    4 of 15 announced prefixes have no ROA (RPKI not found): 2a14:7580:71c::/48, 2a14:7580:71e::/48, 2a14:7580:711::/48, 2a14:7580:c16::/48.

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

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

    2a14:7580:71c::/48 AS204539 max-length /48
    2a14:7580:71e::/48 AS204539 max-length /48
    2a14:7580:711::/48 AS204539 max-length /48
    2a14:7580:c16::/48 AS204539 max-length /48

    Open in RPKI / ROA validator Guide

  2. Warning

    1 of 15 announced prefixes have no IRR route object: 2a0f:1cc5:e21::/48.

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

    route6: 2a0f:1cc5:e21::/48
    origin: AS204539

    Open in ASN & BGP prefix lookup

Checks

Routing and RPKI 4 of 15 announced prefixes have no ROA (RPKI not found): 2a14:7580:71c::/48, 2a14:7580:71e::/48, 2a14:7580:711::/48, 2a14:7580:c16::/48.
  • Pass: AS204539 announces 1 IPv4 and 14 IPv6 prefixes.
  • Warning: 4 of 15 announced prefixes have no ROA (RPKI not found): 2a14:7580:71c::/48, 2a14:7580:71e::/48, 2a14:7580:711::/48, 2a14:7580:c16::/48.
  • Info: 11 of 15 announced prefixes are RPKI valid.
  • Warning: 1 of 15 announced prefixes have no IRR route object: 2a0f:1cc5:e21::/48.
  • Info: 25 upstreams and peers, 9 downstream networks seen.
HolderAXIC-Axivora-Connect-Ltd Axivora Connect Ltd
IPv4 prefixes1
IPv6 prefixes14
RPKI11 valid · 4 not found
Without IRR route object1
Downstream networks9
Routes to fix

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.
NameAXIC-Axivora-Connect-Ltd
HandleAS204539
RangeAS204539
Statusactive
Registered2025-10-23T08:59:10Z
Last changed2026-04-16T21:37:02Z
Abuse contactaudit@axivora.net
Allocation
Registry (RIR)RIPE NCC
CountryUnited Kingdom (GB)
Delegated on2025-10-23
StatusAllocated
Delegated rangeAS204539

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

Contacts
RoleNameEmail
registrant AXIVORA-MNT
registrant MOEDOVE-MNT
registrant Axivora Connect Ltd
registrant RIPE-NCC-END-MNT
abuse Axivora Connect Ltd RIPE Maintainer audit@axivora.net

Source: https://rdap.db.ripe.net/autnum/204539. 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 AS204539 is in PeeringDB as AXIC(Axivora Connect LtD).
  • Pass: AS204539 is in PeeringDB as AXIC(Axivora Connect LtD).
  • Info: Peering policy: Open.
  • Info: Present at 7 internet exchanges with 9 ports (81G in total).
NetworkAXIC(Axivora Connect LtD) (AXIC)
AS numberAS204539
TypeCable/DSL/ISP, Global
Websitehttps://axivora.uk
IRR as-setAS-AXIC
Prefixes (IPv4 / IPv6)250 / 1500
Traffic100-200Gbps, Balanced
Peering policyOpen
LocationsNot Required
Ratio requiredNo
ContractsNot Required
Last updated2026-06-09
Contacts
Abusenoc@axivora.net
NOCnoc@axivora.net rym@axivora.net orion_ml.huang@axivora.net
Maintenancenoc@axivora.net

Source: PeeringDB. Results are cached for an hour.

Open in PeeringDB lookup