SUBNET.IM

31.131.82.0/24

Gerkon LTDAS42498

TTC Radiotechnika LTDAS56889

Announced by more than one origin AS (MOAS).

At a glance

Addresses

256

/24 block

Visibility

89%

71 of 80 vantage points

RPKI

No ROA

Registry

RIPE NCCRU

Allocated 3rd June 2011

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 31.131.82.0/24, fanning out from AS42498, AS56889 toward the vantage points that see it. Each path is written out in full beneath the graph.AS56889TTC Radiotechnika…OriginAS42498Gerkon LTDAS6939Hurricane Electri…AS20130Depaul UniversityAS42498Gerkon LTDOriginAS56889TTC Radiotechnika…AS42498Gerkon LTDAS9002RETN LimitedAS8529Zain Omantel Inte…AS3356Lumen (Level 3)AS266213PLANETCLICK TELEC…AS12389Rostelecom PJSCAS4766Korea TelecomAS132337AxclusiveAS6453TATA Communicatio…AS34549meerfarbig GmbH &…AS213151Christian Elsen
  1. Oregon, US5688942498693920130This path
  2. London, UK42498568894249890028529This path
  3. Sao Paulo42498568894249890023356266213This path
  4. Singapore424985688942498123894766132337This path
  5. Amsterdam4249856889424989002645334549213151This 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

89%

Seen by 71 of 80 full-feed vantage points

Partially 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
3rd June 2011
Allocation block
31.131.80.0/21
Status
assigned
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 31.131.82.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.31.131.80.0/21AS4249831.131.80.0/21AS5688931.131.83.0/24AS4249831.131.82.0/24AS42498This prefix31.131.83.0/24AS56889

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 31.131.82.0/24
PrefixAddressesOriginVisibility
31.131.80.0/212kAS42498Gerkon LTD71/80
31.131.80.0/212kAS56889TTC Radiotechnika LTD9/80

More specific announcements

Nothing inside this block is announced separately.

Sibling prefixes

Prefixes of the same length sharing a parent block with 31.131.82.0/24
PrefixAddressesOriginVisibility
31.131.83.0/24256AS42498Gerkon LTD71/80
31.131.83.0/24256AS56889TTC Radiotechnika LTD9/80

History

  1. AS5688912th August 2026 — present
  2. AS4249812th 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 31.131.82.0/24 in the calculator/24 reference

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