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

AS210152 · 

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

Problem: AS210152 (VANVIK-INTERNET) announces 2 IPv4 and 3 IPv6 prefixes. 1 problem · 2 warnings

AS pageAS210152
HolderVANVIK-INTERNET Jon Vanvik trading as Vanvik Internet
AllocationRIPE NCC, Norway (NO), allocated 2022-08-15
Prefixes (IPv4 / IPv6)2 / 3
RPKI valid80% (4 / 5)
Upstreams and peers4
Peering policyOpen

What to fix

  1. Problem

    1 of 5 announced prefixes are RPKI invalid: 185.249.254.0/24.

    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

    1 of 5 announced prefixes have no IRR route object: 185.249.254.0/24.

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

    route: 185.249.254.0/24
origin: AS210152

    Open in ASN & BGP prefix lookup

  3. 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 1 of 5 announced prefixes are RPKI invalid: 185.249.254.0/24.
  • Pass: AS210152 announces 2 IPv4 and 3 IPv6 prefixes.
  • Problem: 1 of 5 announced prefixes are RPKI invalid: 185.249.254.0/24.
  • Info: 4 of 5 announced prefixes are RPKI valid.
  • Warning: 1 of 5 announced prefixes have no IRR route object: 185.249.254.0/24.
  • Info: 4 upstreams and peers, 9 downstream networks seen.
HolderVANVIK-INTERNET Jon Vanvik trading as Vanvik Internet
IPv4 prefixes2
IPv6 prefixes3
RPKI4 valid · 1 invalid
Without IRR route object1
Downstream networks9
Routes to fix
PrefixRPKI
185.249.254.0/24 RPKI invalid

Upstreams and peers seen to the left 4

AS6939 Hurricane Electric AS206260 SVORKA Bredbånd AS56655 Gigahost AS AS212514 SpanningNetworks AS

Announced prefixes 5

185.147.35.0/24 185.249.254.0/24 2a0a:3e40::/29 2a0a:3e42::/32 2a01:ffc6:4000::/48

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.
NameVANVIK-INTERNET
HandleAS210152
RangeAS210152
Statusactive
Registered2022-08-15T11:03:23Z
Last changed2026-10-09T11:46:44Z
Abuse contactabuse@vanvikinternet.no
Allocation
Registry (RIR)RIPE NCC
CountryNorway (NO)
Delegated on2022-08-15
StatusAllocated
Delegated rangeAS210152

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

Contacts
RoleNameEmail
registrant Jon Vanvik trading as Vanvik Internet
registrant RIPE-NCC-END-MNT
registrant VANVIK-EU-MNT
abuse Abuse-C Role abuse@vanvikinternet.no

Source: https://rdap.db.ripe.net/autnum/210152. 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 public NOC, policy or technical contact.
  • Pass: AS210152 is in PeeringDB as VANVIK INTERNET.
  • Info: Peering policy: Open.
  • Info: Present at 2 internet exchanges with 2 ports (1.1G in total).
  • Warning: No public NOC, policy or technical contact.
NetworkVANVIK INTERNET (VANVIK INTERNET)
AS numberAS210152
TypeNSP, Regional
Websitehttp://vanvik.eu
IRR as-setAS-VANVIK
Prefixes (IPv4 / IPv6)10 / 100
Traffic1-5Gbps, Balanced
Peering policyOpen
LocationsNot Required
Ratio requiredNo
ContractsNot Required
Last updated2026-08-10

Source: PeeringDB. Results are cached for an hour.

Open in PeeringDB lookup