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

AS42183 · 

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

Warning: AS42183 (net360 NET 360 S.A.R.L) announces 4 IPv4 and 0 IPv6 prefixes. 3 warnings

AS pageAS42183
Holdernet360 NET 360 S.A.R.L
AllocationRIPE NCC, Lebanon (LB), allocated 2014-12-24
Prefixes (IPv4 / IPv6)4 / 0
RPKI valid100% (4 / 4)
Upstreams and peers1
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

    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

  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 No IPv6 prefixes announced.
  • Pass: AS42183 announces 4 IPv4 and 0 IPv6 prefixes.
  • Warning: No IPv6 prefixes announced.
  • Pass: All 4 announced prefixes are RPKI valid.
  • Pass: Every announced prefix has an IRR route object.
  • Info: One upstream or peer seen (AS42020): an outage there takes the whole network off the internet.
Holdernet360 NET 360 S.A.R.L
IPv4 prefixes4
IPv6 prefixes0
RPKI4 valid
Downstream networks0

Upstreams and peers seen to the left 1

AS42020 LibanTelecom

Announced prefixes 4

185.82.96.0/24 185.82.97.0/24 185.82.98.0/24 185.82.99.0/24

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.
Namenet360
HandleAS42183
RangeAS42183
Statusactive
Registered2014-12-24T11:39:32Z
Last changed2026-03-23T13:31:08Z
Abuse contactnoc@net360.net.lb
Allocation
Registry (RIR)RIPE NCC
CountryLebanon (LB)
Delegated on2014-12-24
StatusAllocated
Delegated rangeAS42183

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

Contacts
RoleNameEmail
registrant NOC-Net360
registrant NET 360 S.A.R.L
registrant RIPE-NCC-END-MNT
abuse ABUSE Net360 noc@net360.net.lb

Source: https://rdap.db.ripe.net/autnum/42183. 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: AS42183 is in PeeringDB as NET 360.
  • 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.
NetworkNET 360
AS numberAS42183
Type, Middle East
Websitehttp://net360.net.lb
Prefixes (IPv4 / IPv6)4 / 1
Traffic1-5Gbps, Heavy Inbound
Peering policyOpen
LocationsRequired - EU
Ratio requiredNo
ContractsPrivate Only
Last updated2022-07-27

Source: PeeringDB. Results are cached for an hour.

Open in PeeringDB lookup