200.141.180.0/23
At a glance
Addresses
/23 block
Visibility
76 of 76 vantage points
RPKI
Registry
AEAllocated 13th March 2025
AS paths to this prefix
All pathsOne observed path, hop by hop, from the origin out to Oregon, US.
Seen from Oregon, US
- Peer of AS275761seen on 45 paths from 45 vantage points
- Peer of AS52925seen on 12,908 paths from 119 vantage points
- Peer of AS4230seen on 4,141 paths from 1 vantage point
- Peer of AS8551seen on 1,077,002 paths from 1 vantage point
BR
IL
PSOne 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
- Sao Paulo2757615292535280This path
- Amsterdam2757615292542308298This path
- London, UK27576126640069398529This path
- Singapore2757612664003356349123673This path
- Oregon, US275761529254230855142013Shown 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 76 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
- United Arab Emirates
- Allocated
- 13th March 2025
- Allocation block
- 200.141.176.0/20
- 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 |
|---|---|---|
| 200.141.180.0/23 | AS275761 | /24 |
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 |
|---|---|---|---|
| 200.141.180.0/24 | 256 | AS275761HOSTEG HOSPEDAGEM E SERVIDORES LTDA | 76/76 |
| 200.141.181.0/24 | 256 | AS275761HOSTEG HOSPEDAGEM E SERVIDORES LTDA | 76/76 |
Sibling prefixes
No prefix of the same length in the same parent block is announced.
History
- AS27576122nd September 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 200.141.180.0/23 in the calculator/23 reference
Routing data derived from RouteViews MRT archives and public registry data.