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

AS47337 ·

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

Warning: AS47337 announces 2 IPv4 and 0 IPv6 prefixes. 4 warnings

AS pageAS47337
AllocationRIPE NCC, Switzerland (CH), allocated 2008-06-04
Prefixes (IPv4 / IPv6)2 / 0
RPKI valid50% (1 / 2)
Upstreams and peers2

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

    1 of 2 announced prefixes have no ROA (RPKI not found): 195.182.53.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 AS47337 and a max length equal to the prefix length:

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

Upstreams and peers seen to the left 2

Announced prefixes 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.
NameUPLINK-NETWORK
HandleAS47337
RangeAS47337
Statusactive
Registered2008-06-04T12:27:28Z
Last changed2026-09-30T12:54:27Z
Abuse contactabuse@uplink.ch
Allocation
Registry (RIR)RIPE NCC
CountrySwitzerland (CH)
Delegated on2008-06-04
StatusAllocated
Delegated rangeAS47337

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

Contacts
RoleNameEmail
registrant MNT-UPLINKAG
registrant Uplink AG
registrant RIPE-NCC-END-MNT
registrant VTX-MNT
abuse Abuse-C Role abuse@uplink.ch

Source: https://rdap.db.ripe.net/autnum/47337. 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: AS47337 is in PeeringDB as Uplink.
  • 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-12-04.
NetworkUplink
AS numberAS47337
Type, Not Disclosed
Prefixes (IPv4 / IPv6)0 / 0
TrafficNot Disclosed
Ratio requiredNo
Last updated2022-12-04

Source: PeeringDB. Results are cached for an hour.

Open in PeeringDB lookup