153.76.12.0/24
At a glance
Addresses
/24 block
Visibility
55 of 76 vantage points
RPKI
Registry
CAAllocated 23rd September 1991
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 AS205941seen on 1,069 paths from 139 vantage points
- Peer of AS207252seen on 3,489 paths from 130 vantage points
- Peer of AS50629seen on 7,890 paths from 65 vantage points
- Peer of AS2914seen on 439,597 paths from 6 vantage points
RO
DE
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
- Amsterdam205941207252506298298This path
- Singapore20446420594121645623673This path
- London, UK20594120725257575338918529This path
- Sao Paulo20594120725250629291435280Shown above
- Oregon, US2059412072525757533891855142013This 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
72%
Seen by 55 of 76 full-feed vantage points
Partially propagatedObserved at 4 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
- Canada
- Allocated
- 23rd September 1991
- Allocation block
- 153.76.0.0/19
- Status
- assigned
- 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.
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
| Prefix | Addresses | Origin | Visibility |
|---|---|---|---|
| 153.76.8.0/21 | 2k | AS62513GoCodeIT Inc | 30/76 |
| 153.76.0.0/19 | 8.2k | AS835GoCodeIT Inc | 76/76 |
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
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 153.76.12.0/24 in the calculator/24 reference
Routing data derived from RouteViews MRT archives and public registry data.