SUBNET.IM

84.18.96.0/24

PJSC "TATTELECOM"AS28840

At a glance

Addresses

256

/24 block

Visibility

100%

80 of 80 vantage points

RPKI

No ROA

Registry

RIPE NCCRU

Allocated 12th August 2004

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: 5 observed paths to 84.18.96.0/24, fanning out from AS28840 toward the vantage points that see it. Each path is written out in full beneath the graph.AS28840PJSC "TATTELECOM"OriginAS31133MegaFon PJSCAS213151Christian ElsenAS8529Zain Omantel Inte…AS132337AxclusiveAS6939Hurricane Electri…AS20130Depaul UniversityAS6762Telecom Italia Sp…AS3356Lumen (Level 3)AS266213PLANETCLICK TELEC…
  1. Amsterdam2884031133213151This path
  2. London, UK28840311338529This path
  3. Singapore2884031133132337This path
  4. Oregon, US2884031133693920130This path
  5. Sao Paulo288403113367623356266213This 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

100%

Seen by 80 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
Russia
Allocated
12th August 2004
Allocation block
84.18.96.0/19
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 84.18.96.0/24: the announcements covering it on the left, the announcements inside it on the right. Every prefix drawn is also listed in the tables below.84.18.96.0/22AS2884084.18.96.0/19AS2884084.18.96.0/24AS28840This prefix84.18.97.0/24AS28840

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 84.18.96.0/24
PrefixAddressesOriginVisibility
84.18.96.0/221kAS28840PJSC "TATTELECOM"80/80
84.18.96.0/198.2kAS28840PJSC "TATTELECOM"80/80

More specific announcements

Nothing inside this block is announced separately.

Sibling prefixes

Prefixes of the same length sharing a parent block with 84.18.96.0/24
PrefixAddressesOriginVisibility
84.18.97.0/24256AS28840PJSC "TATTELECOM"80/80

History

  1. AS2884012th 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 84.18.96.0/24 in the calculator/24 reference

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