212.36.210.0/24
At a glance
Addresses
/24 block
Visibility
76 of 76 vantage points
RPKI
Registry
LBAllocated 12th August 1998
AS paths to this prefix
All pathsOne observed path, hop by hop, from the origin out to Oregon, US.
Seen from Oregon, US
- Peer of AS24634seen on 4,483 paths from 76 vantage points
- Peer of AS42020seen on 59,698 paths from 138 vantage points
- Peer of AS3356seen on 636,722 paths from 66 vantage points
- Peer of AS1299seen on 324,155 paths from 1 vantage point
- Peer of AS8551seen on 1,076,486 paths from 1 vantage point
US
SE
IL
PSOne path, hop by hop, from the origin outward to the vantage point that saw it. Counts beside each step are how often we see that pair adjacent anywhere in the table, not how often this path was used — BGP carries no traffic figures.
Every path we see
- London, UK246344202033568529This path
- Sao Paulo2463442020335635280This path
- Singapore2463442020335623673This path
- Amsterdam24634420203356250918298This path
- Oregon, US246344202033561299855142013Shown above
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 76 of 76 full-feed vantage points
Globally propagatedObserved 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
- 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.
Prefix hierarchy
Announcements above, below and beside this one in the real routing table.
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
| Prefix | Addresses | Origin | Visibility |
|---|---|---|---|
| 212.36.192.0/19 | 8.2k | AS9051IncoNet Data Management sal | 76/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
- AS246346th November 2026 — present
- AS246345th November 2026 — 6th November 2026
- AS246343rd November 2026 — 5th November 2026
- AS246342nd November 2026 — 3rd November 2026
- AS246341st November 2026 — 2nd November 2026
- AS2463431st October 2026 — 1st November 2026
- AS2463430th October 2026 — 31st October 2026
- 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.