119.252.212.0/23
At a glance
Addresses
/23 block
Visibility
76 of 76 vantage points
RPKI
Registry
INAllocated 13th March 2008
AS paths to this prefix
All pathsOne observed path, hop by hop, from the origin out to Sao Paulo.
Seen from Sao Paulo
- Peer of AS134375seen on 4,214 paths from 139 vantage points
- Peer of AS9583seen on 20,747 paths from 99 vantage points
- Peer of AS2914seen on 439,597 paths from 6 vantage points
US
FROne 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 Paulo1343759583291435280Shown above
- Amsterdam134375958355836640498298This path
- London, UK1343759583475564538529This path
- Singapore1343759583558366404923673This path
- Oregon, US13437595835583664049855142013This 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
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
- APNIC — Asia-Pacific
- Country
- India
- Allocated
- 13th March 2008
- Allocation block
- 119.252.192.0/19
- 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 |
|---|---|---|
| 119.252.212.0/23 | AS134375 | /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 |
|---|---|---|---|
| 119.252.212.0/24 | 256 | AS45148Digivision Entertainment Private Limited | 1/76 |
| 119.252.212.0/24 | 256 | AS134375Fusionnet Web Services Limited | 4/76 |
| 119.252.213.0/24 | 256 | AS134375Fusionnet Web Services Limited | 4/76 |
Sibling prefixes
| Prefix | Addresses | Origin | Visibility |
|---|---|---|---|
| 119.252.214.0/23 | 512 | AS45148Digivision Entertainment Private Limited | 76/76 |
History
- AS1343755th October 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 119.252.212.0/23 in the calculator/23 reference
Routing data derived from RouteViews MRT archives and public registry data.