213.177.186.0/24
At a glance
Addresses
/24 block
Visibility
81 of 82 vantage points
RPKI
Registry
TRAllocated 9th January 2026
AS paths to this prefix
All pathsOne observed path, hop by hop, from the origin out to Sao Paulo.
Seen from Sao Paulo
- Peer of AS62425seen on 2,687 paths from 147 vantage points
- Peer of AS42216seen on 8,902 paths from 146 vantage points
- Peer of AS42910seen on 17,153 paths from 135 vantage points
- Peer of AS208972seen on 50,755 paths from 143 vantage points
- Peer of AS6204seen on 21,537 paths from 52 vantage points
- Peer of AS2914seen on 446,646 paths from 6 vantage points
RO
US
FROne 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
- Oregon, US62425204457693920130This path
- Singapore62425422164291020897244901132337This path
- Amsterdam6242542216429102089724490148498298This path
- London, UK6242542216429102089726204129935280This path
- Sao Paulo6242542216429102089726204291435280Shown 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
99%
Seen by 81 of 82 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
- Türkiye
- Allocated
- 9th January 2026
- Allocation block
- 213.177.186.0/24
- 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 |
|---|---|---|
| 213.177.186.0/24 | AS62425 | /24 |
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
No prefix of the same length in the same parent block is announced.
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 213.177.186.0/24 in the calculator/24 reference
Routing data derived from RouteViews MRT archives and public registry data.