SUBNET.IM

37.98.154.0/23

LLC Babilon-TAS24722

At a glance

Addresses

512

/23 block

Visibility

99%

79 of 80 vantage points

RPKI

No ROA

Registry

RIPE NCCTJ

Allocated 6th February 2012

AS paths to this prefix

One real path per vantage point, fanning out from the origin. Where two reach the prefix the same way, those hops are drawn once. Open a path to follow it hop by hop.

OriginVantage points
AS path graph: 4 observed paths to 37.98.154.0/23, fanning out from AS24722 toward the vantage points that see it. Each path is written out in full beneath the graph.AS24722LLC Babilon-TOriginAS204106CJSC Babilon-Mobi…AS51346Opened Joint Stoc…AS12389Rostelecom PJSCAS8529Zain Omantel Inte…AS6939Hurricane Electri…AS213151Christian ElsenAS4766Korea TelecomAS132337AxclusiveAS3491PCCW Global (HK) …AS3356Lumen (Level 3)AS266213PLANETCLICK TELEC…
  1. London, UK2472220410651346123898529This path
  2. Amsterdam2472220410651346123896939213151This path
  3. Singapore2472220410651346123894766132337This path
  4. Sao Paulo24722204106513461238934913356266213This path

Each row is one path genuinely present in the routing table at our last snapshot, read outward from the origin to the vantage point that saw it. Open a row to follow that one path hop by hop. A heavier line in the graph means more vantage points reach the prefix that same way.

Route visibility

99%

Seen by 79 of 80 full-feed vantage points

Globally propagated

Observed at 5 of our collectors.

What this percentage counts

The denominator counts only full-feed peers — peers carrying a substantially complete routing table at the moment of the snapshot. IXP route-server peers usually feed partial tables and are excluded, because including them would make a normally propagated prefix look as though half the internet could not see it.

It measures how widely an announcement has spread across the networks we can observe. It says nothing about whether the prefix is reachable from any particular place, or how it performs.

Registry and RPKI

RIR
RIPE NCC — Europe, Middle East, Central Asia
Country
Tajikistan
Allocated
6th February 2012
Allocation block
37.98.152.0/21
Status
allocated
Origin validation
No ROA

No ROA covers this prefix, so RPKI has nothing to say about it either way. This is still the common case for a large share of the routing table.

Prefix hierarchy

Announcements above, below and beside this one in the real routing table.

CoveringMore specific
Prefix hierarchy for 37.98.154.0/23: the announcements covering it on the left, the announcements inside it on the right. Every prefix drawn is also listed in the tables below.37.98.152.0/21AS2472237.98.154.0/23AS24722This prefix37.98.154.0/24AS2472237.98.155.0/24AS24722

Left to right is specificity: a shorter mask covering more address space, then this prefix, then the announcements carved out inside it. Only the first few of each are drawn — the tables below list them all.

Covering announcements

Announcements that contain 37.98.154.0/23
PrefixAddressesOriginVisibility
37.98.152.0/212kAS24722LLC Babilon-T79/80

More specific announcements

Announcements contained within 37.98.154.0/23
PrefixAddressesOriginVisibility
37.98.154.0/24256AS24722LLC Babilon-T79/80
37.98.155.0/24256AS24722LLC Babilon-T80/80

Sibling prefixes

No prefix of the same length in the same parent block is announced.

History

  1. AS2472212th August 2026 — present
Why these dates start where they do

A first-seen date is the first time we saw that origin, not the first time it appeared in BGP. Our history is forward-only with no backfill, so it says nothing about the period before we started collecting — treat the earliest dates with suspicion.

Open 37.98.154.0/23 in the calculator/23 reference

Routing data derived from RouteViews MRT archives and public registry data.