asn.dev

Autonomous system

AS34032 SPIDER

Unclassified APNIC

IPv4 addresses 768 2 prefixes
IPv6 prefixes 0 counted as prefixes, not addresses
Countries 1 mostly LB
Exchanges 0 recorded by PCH
Upstreams 1 0 downstream
Flagged prefixes 0 none

Summary

Spider Net

Lebanon · AI-generated

isp lebanon small

SPIDER is operated by Spider Net & Co. SARL.

What it's used for

  • The address space carries the netname LB-SPIDER-20150501 for both announced prefixes, indicating a single organizational estate.
  • With 768 IPv4 addresses across 2 prefixes and only 1 observed neighbour, the ratio suggests a small access or local service provider rather than a transit hub.

Notable

  • Registrants for both prefixes match the AS holder, SPIDER NET & CO. SARL.
  • The inventory consists of two IPv4 blocks: 185.98.206.0/23 and 185.98.204.0/24.
  • No IPv6 prefixes are announced in the inventory.

This description is AI-generated, best-effort context — not authoritative, and provided without any guarantee of accuracy. Source, and how to suggest an edit.

Interconnection

Peering at a glance

Full topology · Graph

Internet exchanges

No exchange port on file. Many exchanges publish no participant list, so this is not proof of absence.

Transit providers

1 upstream, 0 downstream and 1 adjacent networks observed; most-used upstreams first.

ASNetworkPaths seen
AS42020OGERO177

Exchange presence is recorded rather than inferred: the directory collected by Packet Clearing House (https://www.pch.net/ixp/data) on 2026-10-10, licensed CC BY-NC-SA 3.0. Transit is inferred from observed BGP paths, never declared by either party.

Address space

Summary

Shape and geography

IPv4 2 prefixes · 768 addresses IPv6 0 prefixes

CountryNamePrefixes
LBLebanon2

Registry

Allocation record

APNIC · via Atlas (registry + RDAP)
Registry
APNIC
Handle
AS34032
Registry name
Spider
Registrant
MNT-SPIDERNET
Abuse contact
spidernetisp@hotmail.com
Registered
2015-05-06
Last changed
2018-09-04
Allocation
allocated

Declared

PeeringDB profile

self-reported
Name
SPIDER NET
Scope
Not Disclosed
Traffic ratio
Not Disclosed
Peering policy
Open

PeeringDB records are maintained by the network operator and are not independently verified. Treat them as a statement of intent rather than of fact. For the observed and recorded view, see peering, which lists the exchanges Packet Clearing House has a port on file for.

Routing security

RPKI and IRR

Full detail
RPKI
100% valid · 3 valid, 0 with no ROA
ROAs
4 authorising AS34032
ASPA
no ASPA record
IRR
100% registered · 3 of 3 announcements
Route objects
5 naming AS34032

Reputation

Classification and threat

Unclassified Not in the curated lists. Most of the ~80,000 allocated ASNs are not.

Spamhaus DROP

Not on ASN-DROP The network as a whole is not listed.

No DROP prefixes None of its announced space is on the DROP prefix list.

Spamhaus DROP ("Don't Route Or Peer") lists space and networks run by, or hijacked for, spam and cybercrime operations: 431 networks and 1,775 prefixes, as published 2026-10-11. A short, high-confidence list, so a match is worth taking seriously, and absence from it says little on its own.

FBI IC3

No IC3 indicators Nothing from the FBI IC3 feed.

IC3 threat data is alpha. Absence of an indicator is not evidence of good behaviour, only of absence from this one feed.

Elsewhere

Cross-check