185.149.233.0/24
At a glance
Addresses
/24 block
Visibility
81 of 81 vantage points
RPKI
Registry
CAAllocated 23rd January 2019
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 AS208949seen on 81 paths from 81 vantage points
- Peer of AS34534seen on 1,602 paths from 144 vantage points
- Peer of AS49434seen on 5,662 paths from 77 vantage points
- Peer of AS9002seen on 219,991 paths from 29 vantage points
- Peer of AS6453seen on 666,978 paths from 6 vantage points
GB
FR
USOne 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
- Amsterdam20894934534494348298This path
- London, UK208949345344943435280This path
- Singapore2089493453449434132337This path
- Oregon, US2089493453449434693920130This path
- Sao Paulo20894934534494349002645335280Shown 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 81 of 81 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
- Canada
- Allocated
- 23rd January 2019
- Allocation block
- 185.149.232.0/22
- 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 |
|---|---|---|---|
| 185.149.232.0/22 | 1k | AS62164Heymman Servers Corporation | 80/81 |
More specific announcements
Nothing inside this block is announced separately.
Sibling prefixes
| Prefix | Addresses | Origin | Visibility |
|---|---|---|---|
| 185.149.232.0/24 | 256 | AS62164Heymman Servers Corporation | 80/81 |
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.149.233.0/24 in the calculator/24 reference
Routing data derived from RouteViews MRT archives and public registry data.