79.179.195.0/24
AS64976 is not currently observed originating this prefix. The origins we do see are listed above.
At a glance
Addresses
/24 block
Visibility
22 of 78 vantage points
RPKI
Registry
ILAllocated 14th June 2007
AS paths to this prefix
All pathsOne observed path, hop by hop, from the origin out to Oregon, US.
Seen from Oregon, US
- Peer of AS8551seen on 21,791 paths from 95 vantage points
- Peer of AS3356seen on 92,295 paths from 27 vantage points
- Peer of AS6762seen on 33,420 paths from 1 vantage point
- Peer of AS1680seen on 35,750 paths from 1 vantage point
US
IT
PSOne 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
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
28%
Seen by 22 of 78 full-feed vantage points
Seen by few vantage pointsObserved at 2 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
- Israel
- Allocated
- 14th June 2007
- Allocation block
- 79.176.0.0/13
- Status
- allocated
- 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 |
|---|---|---|---|
| 79.179.192.0/20 | 4.1k | AS8551Bezeq International Ltd. | 78/78 |
| 79.179.192.0/19 | 8.2k | AS8551Bezeq International Ltd. | 78/78 |
More specific announcements
Nothing inside this block is announced separately.
Sibling prefixes
| Prefix | Addresses | Origin | Visibility |
|---|---|---|---|
| 79.179.194.0/24 | 256 | AS8551Bezeq International Ltd. | 77/78 |
| 79.179.194.0/24 | 256 | AS64976 | 1/78 |
History
- AS855129th October 2026 — present
- AS6497613th November 2026 — 13th November 2026
- AS6497612th November 2026 — 12th November 2026
- AS649769th November 2026 — 10th November 2026
- AS649768th November 2026 — 8th November 2026
- AS649761st November 2026 — 8th November 2026
- AS6497630th October 2026 — 31st October 2026
- AS6497629th October 2026 — 29th October 2026
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 79.179.195.0/24 in the calculator/24 reference
Routing data derived from RouteViews MRT archives and public registry data.