185.82.136.0/22
At a glance
Addresses
/22 block
Visibility
76 of 76 vantage points
RPKI
Registry
IRAllocated 29th December 2014
AS paths to this prefix
All pathsOne observed path, hop by hop, from the origin out to Singapore.
Seen from Singapore
- Peer of AS206507seen on 228 paths from 76 vantage points
- Peer of AS204650seen on 7,055 paths from 139 vantage points
- Peer of AS42337seen on 144,175 paths from 139 vantage points
- Peer of AS12880seen on 175,720 paths from 139 vantage points
- Peer of AS49666seen on 273,027 paths from 76 vantage points
- Peer of AS29049seen on 15,514 paths from 97 vantage points
- Peer of AS6663seen on 9,257 paths from 106 vantage points
- Peer of AS5405seen on 6,932 paths from 2 vantage points
AZ
RO
DE
KHOne 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
- Amsterdam206507204650423371288049666290498298This path
- London, UK20650720465042337128804966669398529This path
- Sao Paulo20650720465042337128804966629049645335280This path
- Singapore2065072046504233712880496662904966635405→ ⋯Shown above
- Oregon, US20650720465042337128804966629049207648551→ ⋯This 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 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
- Iran
- Allocated
- 29th December 2014
- Allocation block
- 185.82.136.0/22
- Status
- allocated
- Origin validation
- Valid
A ROA exists that authorises this origin AS to announce this prefix at this length.
ROAs covering this prefix
| ROA prefix | Authorised origin | Max length |
|---|---|---|
| 185.82.136.0/22 | AS206507 | /22 |
Prefix hierarchy
Announcements above, below and beside this one in the real routing table.
Covering announcements
No less specific announcement covers this prefix.
More specific announcements
Nothing inside this block is announced separately.
Sibling prefixes
| Prefix | Addresses | Origin | Visibility |
|---|---|---|---|
| 185.82.140.0/22 | 1k | AS42812Internet B.V | 76/76 |
History
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 185.82.136.0/22 in the calculator/22 reference
Routing data derived from RouteViews MRT archives and public registry data.