185.244.240.0/24
At a glance
Addresses
/24 block
Visibility
77 of 82 vantage points
RPKI
Registry
MKAllocated 5th February 2018
AS paths to this prefix
All pathsOne observed path, hop by hop, from the origin out to Singapore.
Seen from Singapore
- Peer of AS206666seen on 897 paths from 82 vantage points
- Peer of AS25467seen on 1,453 paths from 140 vantage points
- Peer of AS6939seen on 366,637 paths from 2 vantage points
SI
US
SGOne 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
- Amsterdam2066662546769398298This path
- London, UK20666625467693935280This path
- Sao Paulo20666625467693935280This path
- Singapore206666254676939132337Shown above
- Oregon, US20666625467693920130This 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
94%
Seen by 77 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
- North Macedonia
- Allocated
- 5th February 2018
- Allocation block
- 185.244.240.0/22
- Status
- allocated
- Origin validation
- No ROA
No ROA covers this prefix, so RPKI has nothing to say about it either way. This is still the common case for a large share of the routing table.
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 |
|---|---|---|---|
| 185.244.241.0/24 | 256 | AS206666MULTIMEDIA-NET DOO SKOPJE | 82/82 |
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.244.240.0/24 in the calculator/24 reference
Routing data derived from RouteViews MRT archives and public registry data.