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

AS56270 ·

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

Warning: AS56270 (ROJAN-AU) announces 4 IPv4 and 0 IPv6 prefixes. 4 warnings

AS pageAS56270
HolderROJAN-AU - ROJAN AUSTRALIA
AllocationAPNIC, Australia (AU), allocated 2011-05-10
Prefixes (IPv4 / IPv6)4 / 0
RPKI valid25% (1 / 4)
Upstreams and peers2
Peering policyOpen

What to fix

  1. Warning

    No IPv6 prefixes announced.

    Networks without IPv6 force their users through NAT64 or leave them unreachable from IPv6-only networks.

    Fix: Get an IPv6 allocation from your RIR (usually free with your IPv4 membership) and announce it.

    Open in ASN & BGP prefix lookup

  2. Warning

    3 of 4 announced prefixes have no ROA (RPKI not found): 103.246.233.0/24, 203.1.10.0/24, 203.1.15.0/24.

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

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

    103.246.233.0/24 AS56270 max-length /24
    203.1.10.0/24 AS56270 max-length /24
    203.1.15.0/24 AS56270 max-length /24

    Open in RPKI / ROA validator Guide

  3. 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

  4. 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 No IPv6 prefixes announced.
  • Pass: AS56270 announces 4 IPv4 and 0 IPv6 prefixes.
  • Warning: No IPv6 prefixes announced.
  • Warning: 3 of 4 announced prefixes have no ROA (RPKI not found): 103.246.233.0/24, 203.1.10.0/24, 203.1.15.0/24.
  • Info: 1 of 4 announced prefixes are RPKI valid.
  • Pass: Every announced prefix has an IRR route object.
  • Info: 2 upstreams and peers, 0 downstream networks seen.
HolderROJAN-AU - ROJAN AUSTRALIA
IPv4 prefixes4
IPv6 prefixes0
RPKI1 valid · 3 not found
Downstream networks0
Routes to fix
PrefixRPKI
103.246.233.0/24 No ROA
203.1.10.0/24 No ROA
203.1.15.0/24 No ROA

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.apnic.net.
  • Pass: Found at rdap.apnic.net.
NameROJAN-AU
HandleAS56270
RangeAS56270
CountryAU
Statusactive
Registered2011-05-10T05:41:37Z
Last changed2020-06-22T06:08:44Z
Abuse contactkevin@rojan.net
Allocation
Registry (RIR)APNIC
CountryAustralia (AU)
Delegated on2011-05-10
StatusAllocated
Delegated rangeAS56270

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

Contacts
RoleNameEmail
administrative, technical ROJAN AUSTRALIA PTY LTD - network administrator admin@rojan.net
registrant Rojan Australia Pty Ltd jopin@rojan.net
abuse IRT-ROJAN-AU kevin@rojan.net

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

Open in WHOIS / RDAP lookup
PeeringDB No IRR as-set is listed.
  • Pass: AS56270 is in PeeringDB as Rojan Australia.
  • Info: Peering policy: Open.
  • 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 2022-07-27.
NetworkRojan Australia
AS numberAS56270
Type, Not Disclosed
Websitehttps://rojan.net/
Prefixes (IPv4 / IPv6)0 / 0
TrafficNot Disclosed
Peering policyOpen
LocationsNot Required
Ratio requiredNo
ContractsNot Required
Last updated2022-07-27

Source: PeeringDB. Results are cached for an hour.

Open in PeeringDB lookup