84.255.184.0/24
AS6453 is not currently observed originating this prefix. The origins we do see are listed above.
At a glance
Addresses
/24 block
Visibility
10 of 81 vantage points
RPKI
Registry
BHAllocated 13th December 2004
AS paths to this prefix
All pathsOne observed path, hop by hop, from the origin out to Amsterdam.
Seen from Amsterdam
- Peer of AS5416seen on 24 paths from 1 vantage point
- Peer of AS16265seen on 99 paths from 2 vantage points
- Peer of AS38930seen on 2,182 paths from 2 vantage points
- Peer of AS8283seen on 64,747 paths from 2 vantage points
NL
CHOne 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
- London, UK541635280This path
- Sao Paulo541635280This path
- Singapore5416158028966132337This path
- Amsterdam5416162653893082838298Shown 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
12%
Seen by 10 of 81 full-feed vantage points
Seen by few vantage pointsObserved at 4 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
- Bahrain
- Allocated
- 13th December 2004
- Allocation block
- 84.255.128.0/18
- 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 |
|---|---|---|---|
| 84.255.184.0/23 | 512 | AS5416BEYON B.S.C. | 81/81 |
| 84.255.184.0/22 | 1k | AS5416BEYON B.S.C. | 81/81 |
| 84.255.184.0/21 | 2k | AS5416BEYON B.S.C. | 81/81 |
| 84.255.160.0/19 | 8.2k | AS5416BEYON B.S.C. | 81/81 |
| 84.255.128.0/18 | 16.4k | AS5416BEYON B.S.C. | 81/81 |
More specific announcements
Nothing inside this block is announced separately.
Sibling prefixes
| Prefix | Addresses | Origin | Visibility |
|---|---|---|---|
| 84.255.185.0/24 | 256 | AS5416BEYON B.S.C. | 79/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 84.255.184.0/24 in the calculator/24 reference
Routing data derived from RouteViews MRT archives and public registry data.