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

AS50084 · 

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

Warning: AS50084 (RAPID-LINK-AS) announces 7 IPv4 and 1 IPv6 prefixes. 2 warnings

AS pageAS50084
HolderRAPID-LINK-AS S.A."Rapid Link" S.R.L.
AllocationRIPE NCC, Moldova (MD), allocated 2009-11-11
Prefixes (IPv4 / IPv6)7 / 1
RPKI valid100% (8 / 8)
Upstreams and peers3
Peering policyOpen

What to fix

  1. Warning

    3 of 8 announced prefixes have no IRR route object: 185.96.177.0/24, 185.96.179.0/24, 185.96.176.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 AS50084 in your RIR’s IRR database (or RADB).

    route: 185.96.177.0/24
origin: AS50084

route: 185.96.179.0/24
origin: AS50084

route: 185.96.176.0/24
origin: AS50084

    Open in ASN & BGP prefix lookup

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

Checks

Routing and RPKI 3 of 8 announced prefixes have no IRR route object: 185.96.177.0/24, 185.96.179.0/24, 185.96.176.0/24.
  • Pass: AS50084 announces 7 IPv4 and 1 IPv6 prefixes.
  • Pass: All 8 announced prefixes are RPKI valid.
  • Warning: 3 of 8 announced prefixes have no IRR route object: 185.96.177.0/24, 185.96.179.0/24, 185.96.176.0/24.
  • Info: 3 upstreams and peers, 8 downstream networks seen.
HolderRAPID-LINK-AS S.A."Rapid Link" S.R.L.
IPv4 prefixes7
IPv6 prefixes1
RPKI8 valid
Without IRR route object3
Downstream networks8

Upstreams and peers seen to the left 3

AS5606 GTS Telecom AS9002 RETN AS14840 BR.Digital

Announced prefixes 8

185.96.176.0/22 185.96.176.0/24 185.96.177.0/24 185.96.178.0/24 185.96.179.0/24 194.247.164.0/24 194.247.165.0/24 2a07:4140::/29

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.
NameRAPID-LINK-AS
HandleAS50084
RangeAS50084
Statusactive
Registered2009-11-11T10:00:39Z
Last changed2025-11-22T08:59:21Z
Abuse contactnoc@rapidlink.md
Allocation
Registry (RIR)RIPE NCC
CountryMoldova (MD)
Delegated on2009-11-11
StatusAllocated
Delegated rangeAS50084

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

Contacts
RoleNameEmail
registrant S.A."Rapid Link" S.R.L.
registrant RAPID-LINK-MNT
registrant RIPE-NCC-END-MNT
abuse Abuse-C Role noc@rapidlink.md

Source: https://rdap.db.ripe.net/autnum/50084. 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: AS50084 is in PeeringDB as RAPIDLINK SRL.
  • Info: Peering policy: Open.
  • Info: Present at 1 internet exchanges with 1 ports (10G in total).
  • Warning: No IRR as-set is listed.
  • Info: The record was last updated 2022-11-17.
NetworkRAPIDLINK SRL
AS numberAS50084
TypeCable/DSL/ISP, Regional
Websitehttp://rapidlink.md
Prefixes (IPv4 / IPv6)10 / 4
Traffic5-10Gbps, Mostly Inbound
Peering policyOpen
Policy URLhttp://rapidlink.md
LocationsPreferred
Ratio requiredNo
ContractsNot Required
Last updated2022-11-17
Contacts
Abusenoc@rapidlink.md
NOCnoc@rapidlink.md

Source: PeeringDB. Results are cached for an hour.

Open in PeeringDB lookup