200.2.112.0/21
At a glance
Addresses
/21 block
Visibility
79 of 80 vantage points
RPKI
Registry
CLAllocated 5th December 1995
AS paths to this prefix
All pathsOne observed path, hop by hop, from the origin out to Singapore.
Seen from Singapore
- Peer of AS11340seen on 134 paths from 18 vantage points
- Peer of AS14259seen on 12,942 paths from 46 vantage points
- Peer of AS262589seen on 43,504 paths from 142 vantage points
- Peer of AS52468seen on 2,903 paths from 1 vantage point
BR
PA
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, UK1134070041295664538529This path
- Sao Paulo113401425926258952468266213This path
- Singapore113401425926258952468132337Shown above
- Oregon, US11340700412956693920130This path
- Amsterdam11340700412956291434549213151This 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
- Chile
- Allocated
- 5th December 1995
- Allocation block
- 200.2.112.0/21
- Status
- assigned
- 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 |
|---|---|---|---|
| 200.2.120.0/21 | 2k | AS27792Wiltel Comunicaciones SA | 80/80 |
History
- AS1134012th 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 200.2.112.0/21 in the calculator/21 reference
Routing data derived from RouteViews MRT archives and public registry data.