BGPVerse by Vautron v0.1.57 (0ea09d57)

Top Autonomous Systems in Jordan

← Top Autonomous Systems · Full list for this country →

Ranked by observed BGP neighbour count. See the full list of all 50 Autonomous Systems registered in Jordan.

  1. #1 AS211826 — ISTQSERVERS-AS Stability for Integrated Server Hosting Ltd 128
  2. #2 AS39526 — MAO Mohammad Ali Obeidat 63
  3. #3 AS9038 — BAT-AS9038 Al Bahrainia al Urdunia Liltaknia Wa Alitisalat Plc. Co 40
  4. #4 AS8697 — JTC-AS8697 Jordan Telecommunications PSC 25
  5. #5 AS48832 — Zain-Jo Jordanian mobile phone services Ltd 25
  6. #6 AS8376 — Jordan Data Communications Company LLC 16
  7. #7 AS47887 — NEU-AS AL-HADATHEH LIL-ITISALAT WA AL-TECHNOLOGIA CO. 15
  8. #8 AS50670 — VTELJO VTEL HOLDINGS LIMITED/JORDAN CO. 8
  9. #9 AS59451 — ARABBANK-AS Al-Bank Al-Arabi PLC. CO. 7
  10. #10 AS33831 — RHC-AS Royal Hashemite Court 4
  11. #11 AS197921 — HBTF Housing Bank for Trade and Finance PLC. 4
  12. #12 AS208336 — BOJ BANK OF JORDAN CO. LTD. 4
  13. #13 AS8934 — NITC National Information Technology Center 3
  14. #14 AS38968 — TAGORG Abu-Ghazaleh Intellectual Property Ltd. 3
  15. #15 AS51958 — RJNetwork The Royal Jordanian Airlines PLC 3
  16. #16 AS60838 — jisb Jordan Islamic Bank Plc. Co. 3
  17. #17 AS201982 — ASMEPSJO Middle East Payment Services Ltd. 3
  18. #18 AS209560 — CapitalBank Capital Bank of Jordan (Limited public shareholding) 3
  19. #19 AS211842 — CAB-JO Cairo Amman Bank PLC 3
  20. #20 AS215270 — madfoatcom Madfoo3atkom for electronic payment co PJSL 3
  21. #21 AS28730 — BLINKAS Broadband Communications LPS 2
  22. #22 AS42912 — XOLJO Al mouakhah lil khadamat al logesteih wa al itisalat 2
  23. #23 AS44702 — JCS-AS JORDANIAN EUROPEAN INTERNET SERVICES CO LLC 2
  24. #24 AS60302 — JordanAhliBank AL-BANK AL-AHLI AL-URDONI PLC 2
  25. #25 AS204327 — network-1 Network International Services Limited Jordan Company LLC 2
  26. #26 AS206060 — unionbank Bank al Etihad Ltd 2
  27. #27 AS206553 — Hikma Al-Hikma Pharmaceuticals LLC 2
  28. #28 AS206608 — IIAB Islamic International Arab Bank PLC 2
  29. #29 AS208148 — jorist Jordanian Experts for Information Security LLC 2
  30. #30 AS209029 — STS-Cloud ZAINTECH SOLUTIONS - JORDAN LLC 2
  31. #31 AS210432 — Extensya-AS Al Mousanada Lckhadamat Al Isnad Wa Marakez Al Itisal Co LPS 2
  32. #32 AS210844 — CSC-JO Credit Card Service Company LPS 2
  33. #33 AS211260 — PteraUni "Petra for education" Limited Public Shareholding 2
  34. #34 AS212042 — as-istqservers Stability for Integrated Server Hosting Ltd 2
  35. #35 AS396076 — jprcjo Jordan Petroleum Refinery PLC 2
  36. #36 AS21088 — FARAH-AS Network Exchange Technology Co. Ltd. 1
  37. #37 AS35282 — ARAMEX-AS Aramex International Services Jordan LLC 1
  38. #38 AS35656 — JUNet Jordanian Universities Network L.L.C. 1
  39. #39 AS48701 — CABAS Cairo Amman Bank PLC 1
  40. #40 AS200666 — PNF_JO Palestine National Fund 1
  41. #41 AS203357 — emkanat Emkanat Co for Software Development 1
  42. #42 AS203931 — ASPUAS Applied Science University (ASU) 1
  43. #43 AS204719 — CapitalBank Capital Bank of Jordan (Limited public shareholding) 1
  44. #44 AS205579 — Warka Al Warka Bank for Investment J.S.C. 1
  45. #45 AS207332 — AIG Airport International Group 1
  46. #46 AS208212 — Virtual-Data-IT Smart Platform for Programming and Education LLC trading as 'Virtual Data IT' 1
  47. #47 AS210084 — JCB Jordan Commercial Bank 1
  48. #48 AS212507 — RHCJO Royal Hashemite Court 1
  49. #49 AS214244 — ajib Arab Jordan investment bank PLC 1
  50. #50 AS218939 — south-solutions ahmad abuhatab 1

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.