45.183.42.0/23
At a glance
Addresses
/23 block
Visibility
79 of 80 vantage points
RPKI
Registry
VEAllocated 5th 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 AS271920seen on 79 paths from 79 vantage points
- Peer of AS266841seen on 678 paths from 80 vantage points
- Peer of AS263703seen on 3,241 paths from 130 vantage points
- Peer of AS19978seen on 18,559 paths from 142 vantage points
- Peer of AS3356seen on 361,679 paths from 38 vantage points
- Peer of AS6939seen on 320,794 paths from 2 vantage points
AR
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
- London, UK2719202668412637031997833568529This path
- Sao Paulo271920266841263703199783356266213This path
- Singapore2719202668412637031997833566939132337Shown above
- Oregon, US271920266841263703199783356693920130This path
- Amsterdam271920266841263703199783356291434549213151This 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 79 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
- LACNIC — Latin America and the Caribbean
- Country
- Venezuela
- Allocated
- 5th September 2019
- Allocation block
- 45.183.42.0/23
- 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.
Covering announcements
No less specific announcement covers this prefix.
More specific announcements
Nothing inside this block is announced separately.
Sibling prefixes
No prefix of the same length in the same parent block is announced.
History
- AS27192012th 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 45.183.42.0/23 in the calculator/23 reference
Routing data derived from RouteViews MRT archives and public registry data.