subnet.im

212.36.210.0/24

Transmog Inc S.A.LAS24634

At a glance

Addresses

256

/24 block

Visibility

28%

21 of 76 vantage points

RPKI

Valid

Registry

RIPE NCCLB

Allocated 12th August 1998

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: 1 observed path to 212.36.210.0/24, fanning out from AS24634 toward the vantage points that see it. Each path is written out in full beneath the graph.AS24634Transmog Inc S.A.LOriginAS42020OGEROAS3356Lumen (Level 3)AS23673Cogetel Online, C…
  1. Singapore2463442020335623673This 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.

Route visibility

28%

Seen by 21 of 76 full-feed vantage points

Seen by few vantage points

Observed at 1 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
Lebanon
Allocated
12th August 1998
Allocation block
212.36.192.0/19
Status
allocated
Origin validation
Valid

A ROA exists that authorises this origin AS to announce this prefix at this length.

ROAs covering this prefix

Route Origin Authorisations covering 212.36.210.0/24
ROA prefixAuthorised originMax length
212.36.192.0/19AS24634/24
212.36.192.0/19AS9051/24

Prefix hierarchy

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

CoveringMore specific
Prefix hierarchy for 212.36.210.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.212.36.192.0/19AS9051212.36.210.0/24AS24634This prefix

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 212.36.210.0/24
PrefixAddressesOriginVisibility
212.36.192.0/198.2kAS9051IncoNet Data Management sal76/76

More specific announcements

Nothing inside this block is announced separately.

Sibling prefixes

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

History

  1. AS246346th November 2026 — present
  2. AS246345th November 2026 — 6th November 2026
  3. AS246343rd November 2026 — 5th November 2026
  4. AS246342nd November 2026 — 3rd November 2026
  5. AS246341st November 2026 — 2nd November 2026
  6. AS2463431st October 2026 — 1st November 2026
  7. AS2463430th October 2026 — 31st October 2026
  8. AS2463429th October 2026 — 30th October 2026
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 212.36.210.0/24 in the calculator/24 reference

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