BGPVerse by Vautron View on the live map v0.1.57 (0ea09d57)

AS57852 — csp CLOUD S P SARL

🇱🇧 Lebanon · RIPE NCC region · approx. 34.54, 36.08

csp CLOUD S P SARL (AS57852) in Lebanon has 1 direct BGP neighbours, ranked #63727 of 88104 by observed links.

#63727 rank by links (of 88104)
1 direct neighbours
4 IPv4 prefixes
0 IPv6 prefixes
1 upstream providers
0 peers
0 downstream customers
0 customer cone size

Copy network summary

A short plain-text summary of this AS, ready to paste into a chat, forum post or ticket.

Prefer JSON? The same facts are at /as/57852/summary.json.

Embed this badge

Show this AS's current stats on your own website, linking back here.

BGPVerse badge for AS57852 — csp CLOUD S P SARL

Network intelligence

0 MOAS prefixes
4 more-specific prefixes
3.0 avg. AS path length (3–3)

Neighbourhood

What's directly and indirectly (up to two hops) connected to AS57852 — the same force-directed layout as the main Topology view, computed fresh on every page load (reload for a different arrangement), with AS57852 itself always centred. Drag to pan, scroll/pinch to zoom, click a dot to jump to that AS's own page. Explore the full interactive map →

AS57852 — csp CLOUD S P SARL AS57852 AS42020 — LibanTelecom OGERO AS42020 AS3356 — LEVEL3 - Level 3 Parent, LLC AS3356 AS5511 — Opentransit Orange S.A. AS5511 AS14789 — CLOUDFLARENET - Cloudflare, Inc. AS14789 AS39010 — TERRANET-AS TerraNet sal AS39010 AS9051 — IncoNet Data Management sal AS9051 AS31126 — SODETEL-AS SODETEL S.A.L. AS31126 AS48847 — Connect WAVES S.A.L AS48847 AS39918 — AZALGROUP Azadea Group Holding SAL AS39918 AS24634 — Cyberia-AS Transmog Inc S.A.L AS24634 AS43019 — farahnet Farah Net S.a.r.l. AS43019 AS41833 — MOSCANET Moscanet SAL AS41833 AS43056 — i-shack iShack SAL AS43056 AS213962 — MES Middle East Services LLC AS213962 AS59989 — thglobalvision16 T.H. Global Vision SARL AS59989 AS60524 — LAF1 Lebanese Armed Forces AS60524 AS49020 — FiberSkynet-asn Elie Achkar trading as FiberSkynet AS49020 AS31037 — WaveNet Wave Net LLC AS31037 AS64443 — skywaves Sky Waves SARL AS64443 AS44189 — MEA Middle East Airlines AirLiban S.A.L. (M.E.A) AS44189 AS199239 — Accesslb Khodor Kanso trading as Access Lebanon AS199239 AS206360 — pescotel Pesco Telecom s.a.l. AS206360 AS42852 — BCDBBN-AS Societe Libanaise pour le developpement et la reconstruction du centre ville de de Beyrouth (Solidere) AS42852 AS42828 — TOPNETLB-AS Top Net SARL AS42828 AS206406 — CBEY C BEYOND s.a.l AS206406 AS209654 — fibernetlb FIBER net lb s.a.r.l AS209654

Announced prefixes

RPKI route-origin validity badge per prefix, from this instance's self-hosted Routinator (see Credits). The full, de-duplicated set seen across every BGP collector this snapshot imports — usually more than the “IPv4/IPv6 prefixes” counts above, which only reflect a single collector's own routing table.

Upstream providers (1)

Networks that this AS is a customer of (inferred from public BGP data by BGPKIT's as2rel dataset, a heuristic, not ground truth).

Geographic footprint

Geolocated (estimated) country of every prefix AS57852 announces, via IP geolocation against DB-IP City Lite — not AS57852's RIR registration country (see the stats above), and not necessarily where its infrastructure physically sits.

What am I looking at?

Autonomous Systems (AS)

An Autonomous System (AS) is a network, or group of networks, run by one organisation — an internet provider, a university, a cloud provider, a company's own network — that has its own block of IP addresses and decides, as a single unit, how traffic enters and leaves it. This page describes exactly one AS; the full interactive map shows all of them at once, as a graph.

What connects ASes: BGP

The "Upstream providers" / "Peers" / "Downstream customers" sections above, and the connections on the full map, are not physical cables; they are observed routing relationships via BGP (Border Gateway Protocol), the protocol that networks use to tell each other which IP address ranges they can reach. See BGP on Wikipedia for the full protocol details.

Upstream / peer / downstream customer

These relationship labels are an inference, not something BGP itself announces directly: BGPKIT's free as2rel dataset infers them from patterns in public BGP data (e.g. whether a path through two networks looks like paid transit or settlement-free peering). Treat it as a useful heuristic, not ground truth. Customer cone size (shown above, where this data covers enough of this AS's own links) counts every AS transitively reachable via downstream customer links only — roughly, how many networks ultimately rely on this AS to reach the rest of the Internet.

MOAS prefixes and more-specific prefixes

MOAS (Multiple Origin AS) means a prefix is announced by more than one AS at the same time — usually anycast or multihoming via two upstreams, occasionally a route leak or hijack; this count alone cannot tell those apart. A more-specific prefix is a smaller sub-block of a broader prefix this AS (or another AS) also announces, e.g. a /25 alongside a /24 covering it — common and usually deliberate traffic engineering, not inherently a problem.

RPKI: is this prefix authorised to be announced?

RPKI (Resource Public Key Infrastructure) lets the holder of a prefix publish a signed ROA (Route Origin Authorization) stating exactly which AS may originate it. Valid: a matching ROA exists. Invalid: a ROA exists but for a different AS or a shorter maximum length. Not Found: no ROA covers this prefix at all — still the normal case for most of the Internet today.

Countries and RIRs

Every AS is registered in one country (RIPE NCC AS names list) and, by extension, in the world region served by one of the five Regional Internet Registries (RIRs) — AFRINIC, APNIC, ARIN, LACNIC and RIPE NCC — the nonprofit bodies that allocate IP address space and AS numbers within their region. Browse by country or by RIR to see every AS registered there.

Full explainer, glossary and data provenance: see the main map's own Help button, or the Credits dialog linked in the footer above.

Privacy & cookies

BGPVerse sets no cookies and uses no analytics, advertising or third-party trackers of any kind.

This page itself stores nothing in your browser (it has no settings of its own to remember). The main interactive map does store your own display preferences (pulse duration, colour mode, etc.) in localStorage — see its own Privacy dialog, reachable from the footer there, to clear that.

Server-side, your IP address is used only transiently (in memory, never written to disk beyond a request-path access log line without the query itself) for rate limiting; see the Credits & data sources dialog for where the map data itself comes from.

Credits & data sources

Operated by

BGPVerse is built and run by Vautron Rechenzentrum AG, a data centre and managed-hosting provider based in Regensburg, Germany — this map is one of our side projects, not a product.

Looking for servers, cloud or network services of your own? Visit vautron.de →

BGP data

“The RIPE Routing Information Service (RIS) is a RIPE NCC service. With the help of network operators all over the world, RIS employs a globally distributed set of Remote Route Collectors (RRCs), typically located at Internet Exchange Points, to collect and store Internet routing data.”

RIPE RIS's own route collectors sit mostly at European/major Internet exchange points; RouteViews (University of Oregon) route collector data fills in several collectors RIS itself has few or none near — Nairobi (KIXP), Johannesburg (NAPAfrica), São Paulo (IX.br), Bangkok (BKNIX) and Hong Kong (HKIX) — for a somewhat broader view of the Internet's edges. Data are archived and made publicly available for download at archive.routeviews.org. Used under its CC BY 4.0 licence.

AS names and registration countries (shown above as each AS's own country, independent of any IP geolocation): RIPE NCC AS names list. RIR (Regional Internet Registry) region assignment is derived from that same registration country via the NRO's own public country-to-RIR table, not a per-resource delegation record, so it is an approximation for the rare legacy/historically-reassigned resource. Approximate AS locations: IP Geolocation by DB-IP (DB-IP City Lite, refreshed daily, derived from a sample of each AS's announced prefixes — not the AS's actual location, and not the same thing as its registration country); the same database also resolves the “Geographic footprint” section above (where appropriate) — a geolocated, estimated country per prefix, again not the registration country — this time against every announced prefix rather than a sample. AS relationships (upstream provider / peer / downstream customer, shown above) are an inference, not ground truth, from BGPKIT's free as2rel dataset, refreshed daily. Icons: a small selection from Font Awesome Free (CC BY 4.0), self-hosted, not loaded from a CDN.

RPKI validation

RPKI route-origin validity badges (prefix list above), when enabled by the operator, are computed by a self-hosted Routinator instance (NLnet Labs, BSD-3-Clause), which fetches and validates Route Origin Authorizations (ROAs) directly from the public RPKI repositories of the five Regional Internet Registries. See the Help dialog for what the badges mean.

Software

Data pipeline status

Whether BGPVerse's own background data pipeline is currently up to date — not just whether the server itself is reachable. Also available as its own page/JSON endpoint: /status.

…

View full AS page