196.43.76.0/24
At a glance
Addresses
/24 block
Visibility
78 of 80 vantage points
RPKI
Registry
TZAllocated 29th January 2009
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 AS33765seen on 8,721 paths from 114 vantage points
- Peer of AS3491seen on 122,201 paths from 47 vantage points
- Peer of AS3356seen on 997,311 paths from 2 vantage points
HK
US
BROne 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, UK33765349112998529This path
- Sao Paulo3376534913356266213Shown above
- Singapore3376534914229132337This path
- Oregon, US337653491693920130This path
- Amsterdam337653491291434549213151This 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
98%
Seen by 78 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
- AFRINIC — Africa
- Country
- Tanzania
- Allocated
- 29th January 2009
- Allocation block
- 196.43.64.0/19
- Status
- allocated
- 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.
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 |
|---|---|---|---|
| 196.43.64.0/19 | 8.2k | AS33765Tanzania Telecommunications Corporation | 80/80 |
More specific announcements
Nothing inside this block is announced separately.
Sibling prefixes
| Prefix | Addresses | Origin | Visibility |
|---|---|---|---|
| 196.43.77.0/24 | 256 | AS33765Tanzania Telecommunications Corporation | 78/80 |
History
- AS3376512th 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 196.43.76.0/24 in the calculator/24 reference
Routing data derived from RouteViews MRT archives and public registry data.