45.149.27.0/24
At a glance
Addresses
/24 block
Visibility
72 of 76 vantage points
RPKI
Registry
UAAllocated 4th September 2019
AS paths to this prefix
All pathsOne observed path, hop by hop, from the origin out to Singapore.
Seen from Singapore
- Peer of AS206668seen on 19 paths from 19 vantage points
- Peer of AS200010seen on 347 paths from 37 vantage points
- Peer of AS4849seen on 10,953 paths from 50 vantage points
- Peer of AS2914seen on 78,227 paths from 1 vantage point
TR
BG
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
- Amsterdam2066682163942124778298This path
- London, UK20666821639421247712998529This path
- Sao Paulo2066682163944849645335280This path
- Singapore2066682000104849291423673Shown above
- Oregon, US206668446202089726204855142013This 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
95%
Seen by 72 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
- Ukraine
- Allocated
- 4th September 2019
- Allocation block
- 45.149.24.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 |
|---|---|---|
| 45.149.27.0/24 | AS206668 | /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 |
|---|---|---|---|
| 45.149.26.0/24 | 256 | AS5511Orange S.A. | 10/76 |
History
- AS20666831st October 2026 — present
- AS19965412th August 2026 — present
- AS234703rd November 2026 — 5th November 2026
- AS2347031st October 2026 — 2nd November 2026
- AS20666820th October 2026 — 31st October 2026
- AS2347020th October 2026 — 20th October 2026
- AS20666819th October 2026 — 19th October 2026
- AS2347012th August 2026 — 19th October 2026
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 45.149.27.0/24 in the calculator/24 reference
Routing data derived from RouteViews MRT archives and public registry data.