89.23.83.0/24
At a glance
Addresses
/24 block
Visibility
75 of 76 vantage points
RPKI
Registry
RSAllocated 24th March 2010
AS paths to this prefix
All pathsOne observed path, hop by hop, from the origin out to Singapore.
Seen from Singapore
- Peer of AS152698seen on 675 paths from 75 vantage points
- Peer of AS62610seen on 60,758 paths from 139 vantage points
- Peer of AS21859seen on 3,061 paths from 138 vantage points
- Peer of AS29752seen on 14,737 paths from 137 vantage points
- Peer of AS3257seen on 248,089 paths from 51 vantage points
- Peer of AS3356seen on 425,047 paths from 2 vantage points
BD
US
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
- Sao Paulo152698626102185929752422935280This path
- Amsterdam1526986261021859297523257250918298This path
- London, UK152698626102185929752325712998529This path
- Singapore1526986261021859297523257335623673Shown above
- Oregon, US15269862610218591741299693920130This 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
99%
Seen by 75 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
- Serbia
- Allocated
- 24th March 2010
- Allocation block
- 89.23.64.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
| ROA prefix | Authorised origin | Max length |
|---|---|---|
| 89.23.83.0/24 | AS152698 | /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
| Prefix | Addresses | Origin | Visibility |
|---|---|---|---|
| 89.23.82.0/24 | 256 | AS204535Tan Kok Feng | 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 89.23.83.0/24 in the calculator/24 reference
Routing data derived from RouteViews MRT archives and public registry data.