196.229.192.0/18
At a glance
Addresses
/18 block
Visibility
77 of 77 vantage points
RPKI
Registry
TNAllocated 21st September 2015
AS paths to this prefix
All pathsOne observed path, hop by hop, from the origin out to Singapore.
Seen from Singapore
- Peer of AS37492seen on 7,271 paths from 107 vantage points
- Peer of AS6762seen on 186,071 paths from 37 vantage points
- Peer of AS3356seen on 424,548 paths from 2 vantage points
IT
US
KHOne 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, UK3749267628529This path
- Amsterdam374926762250918298This path
- Sao Paulo374926762645335280This path
- Singapore374926762335623673Shown above
- Oregon, US374926762693920130This 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 77 of 77 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
- Tunisia
- Allocated
- 21st September 2015
- Allocation block
- 196.224.0.0/12
- 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.229.128.0/17 | 32.8k | AS37492Orange Tunisie | 77/77 |
| 196.224.0.0/12 | 1M | AS37492Orange Tunisie | 76/77 |
More specific announcements
| Prefix | Addresses | Origin | Visibility |
|---|---|---|---|
| 196.229.192.0/19 | 8.2k | AS37492Orange Tunisie | 1/77 |
| 196.229.224.0/19 | 8.2k | AS37492Orange Tunisie | 1/77 |
Sibling prefixes
| Prefix | Addresses | Origin | Visibility |
|---|---|---|---|
| 196.229.128.0/18 | 16.4k | AS37492Orange Tunisie | 77/77 |
History
- AS3749222nd 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 196.229.192.0/18 in the calculator/18 reference
Routing data derived from RouteViews MRT archives and public registry data.