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

AS44486 ·

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

Warning: AS44486 (SYNLINQ) announces 100 IPv4 and 16 IPv6 prefixes. 3 warnings

AS pageAS44486
HolderSYNLINQ Oliver Horscht trading as "SYNLINQ"
AllocationRIPE NCC, Germany (DE), allocated 2019-04-25
Prefixes (IPv4 / IPv6)100 / 16
RPKI valid95% (110 / 116)
Upstreams and peers71
Peering policySelective

What to fix

  1. Warning

    6 of 116 announced prefixes have no ROA (RPKI not found): 5.39.251.0/24, 45.152.160.0/23, 154.43.52.0/22, 154.47.144.0/22, 193.105.200.0/24 (+1).

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

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

    5.39.251.0/24 AS44486 max-length /24
    45.152.160.0/23 AS44486 max-length /23
    154.43.52.0/22 AS44486 max-length /22
    154.47.144.0/22 AS44486 max-length /22
    193.105.200.0/24 AS44486 max-length /24
    2a0c:b641:660::/44 AS44486 max-length /44

    Open in RPKI / ROA validator Guide

  2. Warning

    12 of 116 announced prefixes have no IRR route object: 46.243.76.0/23, 46.243.77.0/24, 46.243.79.0/24, 94.103.170.0/24, 185.13.159.0/24 (+7).

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

    route: 46.243.76.0/23
    origin: AS44486
    
    route: 46.243.77.0/24
    origin: AS44486
    
    route: 46.243.79.0/24
    origin: AS44486

    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 6 of 116 announced prefixes have no ROA (RPKI not found): 5.39.251.0/24, 45.152.160.0/23, 154.43.52.0/22, 154.47.144.0/22, 193.105.200.0/24 (+1).
  • Pass: AS44486 announces 100 IPv4 and 16 IPv6 prefixes.
  • Warning: 6 of 116 announced prefixes have no ROA (RPKI not found): 5.39.251.0/24, 45.152.160.0/23, 154.43.52.0/22, 154.47.144.0/22, 193.105.200.0/24 (+1).
  • Info: 110 of 116 announced prefixes are RPKI valid.
  • Warning: 12 of 116 announced prefixes have no IRR route object: 46.243.76.0/23, 46.243.77.0/24, 46.243.79.0/24, 94.103.170.0/24, 185.13.159.0/24 (+7).
  • Info: 71 upstreams and peers, 15 downstream networks seen.
HolderSYNLINQ Oliver Horscht trading as "SYNLINQ"
IPv4 prefixes100
IPv6 prefixes16
RPKI110 valid · 6 not found
Without IRR route object12
Downstream networks15
Routes to fix

Announced prefixes 116

5.39.251.0/24 5.83.145.0/24 5.175.220.0/24 5.180.252.0/23 5.180.254.0/23 5.231.26.0/24 5.231.221.0/24 5.231.253.0/24 5.253.244.0/24 37.44.215.0/24 37.114.34.0/24 37.114.42.0/24 37.114.43.0/24 37.114.45.0/24 37.114.47.0/24 37.114.48.0/24 37.114.49.0/24 37.114.51.0/24 37.114.52.0/24 37.114.54.0/24 37.114.55.0/24 37.114.56.0/24 37.114.59.0/24 45.67.68.0/24 45.67.69.0/24 45.67.70.0/24 45.67.71.0/24 45.81.232.0/24 45.81.233.0/24 45.81.234.0/24 45.81.235.0/24 45.82.120.0/22 45.84.199.0/24 45.85.219.0/24 45.88.108.0/22 45.91.251.0/24 45.93.248.0/24 45.93.249.0/24 45.93.250.0/24 45.93.251.0/24 45.131.109.0/24 45.132.88.0/24 45.132.89.0/24 45.132.90.0/24 45.132.91.0/24 45.134.108.0/24 45.134.109.0/24 45.135.200.0/22 45.137.71.0/24 45.142.114.0/24 45.142.115.0/24 45.145.224.0/23 45.152.160.0/23 46.243.76.0/23 46.243.77.0/24 46.243.78.0/24 46.243.79.0/24 62.68.75.0/24 77.90.3.0/24 77.90.28.0/24 80.75.218.0/24 85.93.23.0/24 89.106.64.0/24 89.106.76.0/24 89.125.156.0/24 89.144.33.0/24 89.144.42.0/24 91.218.64.0/22 94.103.170.0/24 94.103.172.0/24 94.103.173.0/24 94.249.174.0/24 103.252.88.0/22 109.71.253.0/24 143.14.20.0/24 151.244.232.0/24 154.43.52.0/22 154.47.144.0/22 176.100.32.0/24 176.100.33.0/24 176.100.34.0/24 176.100.35.0/24 176.100.38.0/24 176.116.18.0/24 176.118.193.0/24 185.13.159.0/24 185.14.95.0/24 185.53.249.0/24 185.115.205.0/24 185.132.55.0/24 185.229.248.0/24 185.245.61.0/24 192.35.206.0/24 193.33.167.0/24 193.105.200.0/24 198.135.220.0/24 204.11.1.0/24 212.11.93.0/24 212.87.214.0/23 212.104.211.0/24

Showing the first 100.

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.
NameSYNLINQ
HandleAS44486
RangeAS44486
Statusactive
Registered2019-04-25T10:10:55Z
Last changed2020-10-07T16:08:13Z
Abuse contactabuse@living-bots.net
Allocation
Registry (RIR)RIPE NCC
CountryGermany (DE)
Delegated on2019-04-25
StatusAllocated
Delegated rangeAS44486

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

Contacts
RoleNameEmail
registrant mnt-synlinq
registrant Oliver Horscht trading as "SYNLINQ"
registrant RIPE-NCC-END-MNT
abuse Abuse-C Role abuse@living-bots.net

Source: https://rdap.db.ripe.net/autnum/44486. 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: AS44486 is in PeeringDB as SYNLINQ.
  • Info: Peering policy: Selective.
  • Info: Present at 3 internet exchanges with 3 ports (100G in total).
  • Warning: No public NOC, policy or technical contact.
NetworkSYNLINQ
AS numberAS44486
TypeNSP, Global
Websitehttps://synlinq.de/
IRR as-setAS-SYNLINQ
Prefixes (IPv4 / IPv6)500 / 70
TrafficBalanced
Peering policySelective
LocationsNot Required
Ratio requiredNo
ContractsNot Required
Last updated2026-09-17
Contacts
Salesinfo@synlinq.de

Source: PeeringDB. Results are cached for an hour.

Open in PeeringDB lookup