89.223.78.0/23
At a glance
Addresses
/23 block
Visibility
80 of 80 vantage points
RPKI
Registry
RUAllocated 19th September 2006
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 AS44128seen on 778 paths from 80 vantage points
- Peer of AS33962seen on 762 paths from 68 vantage points
- Peer of AS20485seen on 61,969 paths from 97 vantage points
- Peer of AS1299seen on 600,159 paths from 37 vantage points
- Peer of AS3356seen on 997,311 paths from 2 vantage points
SE
US
BROne 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
- Amsterdam441283396220485213151This path
- London, UK4412833962204858529This path
- Singapore4412833962123894766132337This path
- Oregon, US441283396220485693920130This path
- Sao Paulo44128339622048512993356266213Shown 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 80 of 80 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
- Russia
- Allocated
- 19th September 2006
- Allocation block
- 89.223.76.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 |
|---|---|---|
| 89.223.78.0/23 | AS44128 | /23 |
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
No less specific announcement covers this prefix.
More specific announcements
| Prefix | Addresses | Origin | Visibility |
|---|---|---|---|
| 89.223.79.0/24 | 256 | AS44428HOST EXPERT LLC | 80/80 |
Sibling prefixes
| Prefix | Addresses | Origin | Visibility |
|---|---|---|---|
| 89.223.76.0/23 | 512 | AS44128Internet-Pro LLC | 80/80 |
History
- AS4412812th August 2026 — present
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.223.78.0/23 in the calculator/23 reference
Routing data derived from RouteViews MRT archives and public registry data.