Autonomous system
AS50500 BITARISP2016
Unclassified RIPE
Summary
Bitar Net SARL
isp lebanon small
The AS handle BITARISP2016 is held by Bitar Net SARL.
What it's used for
- The address space carries internet service traffic for a Lebanese operator, identified by netnames
LB-BITAR-20150824andLB-BITAR-20160115. - The network announces 1536 IPv4 addresses across 2 prefixes with only 1 observed neighbour, a ratio indicating a small access or local service provider rather than a transit hub.
- Traffic from this AS consists of subscriber connections for the Bitar Net service area in Lebanon.
Notable
- Registrants for both announced prefixes match the AS holder, Bitar Net SARL.
- The inventory consists of two distinct IPv4 blocks: 185.114.88.0/22 and 185.134.176.0/23.
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
Internet exchanges
Recorded at 1 exchange in 1 country, largest first.
| Exchange | Location | Their address |
|---|---|---|
| OpenIX Beirut | Beirut, Lebanon | 23.181.208.221 |
Transit providers
1 upstream, 0 downstream and 1 adjacent networks observed; most-used upstreams first.
| AS | Network | Paths seen |
|---|---|---|
| AS42020 | OGERO | 354 |
Exchange presence is recorded rather than inferred: the directory collected by Packet Clearing House (https://www.pch.net/ixp/data) on 2026-10-11, licensed CC BY-NC-SA 3.0. Transit is inferred from observed BGP paths, never declared by either party.
Address space
Summary
IPv4 2 prefixes · 1.54K addresses IPv6 0 prefixes
| Country | Name | Prefixes |
|---|---|---|
| LB | Lebanon | 2 |
Registry
Allocation record
- Registry
- RIPE
- Handle
AS50500- Registry name
- bitarisp2016
- Registrant
- lb-bitar-1-mnt
- Abuse contact
- bitarco@hotmail.com
- Registered
- 2016-01-19
- Last changed
- 2021-11-13
- Allocation
- allocated
Declared
PeeringDB profile
- Name
- bitarisp2016
- Scope
- Not Disclosed
- Traffic ratio
- Not Disclosed
- Peering policy
- Open
- Website
- http://bitarnetwork.com
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
- RPKI
- 100% valid · 6 valid, 0 with no ROA
- ROAs
- 8 authorising AS50500
- ASPA
- no ASPA record
- IRR
- 100% registered · 6 of 6 announcements
- Route objects
- 9 naming AS50500
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: 432 networks and 1,768 prefixes, as published 2026-10-12. 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