207.56.12.0/24
At a glance
Addresses
/24 block
Visibility
76 of 76 vantage points
RPKI
Registry
USAllocated 16th February 1996
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 AS18186seen on 2,217 paths from 76 vantage points
- Peer of AS54801seen on 1,970 paths from 76 vantage points
- Peer of AS137983seen on 1,754 paths from 69 vantage points
- Peer of AS3491seen on 113,419 paths from 61 vantage points
- Peer of AS1299seen on 324,212 paths from 1 vantage point
- Peer of AS8551seen on 1,077,043 paths from 1 vantage point
HK
SE
IL
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
- London, UK1818654801137983349112998529This path
- Sao Paulo18186548011379833491645335280This path
- Singapore1818654801137983152475988623673This path
- Amsterdam181865480113798334916762250918298This path
- Oregon, US181865480113798334911299855142013Shown above
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
- ARIN — North America
- Country
- United States
- Allocated
- 16th February 1996
- Allocation block
- 207.56.0.0/15
- 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 |
|---|---|---|---|
| 207.56.0.0/17 | 32.8k | AS18186Nebula Global LLC | 76/76 |
| 207.56.0.0/16 | 65.5k | AS18186Nebula Global LLC | 76/76 |
| 207.56.0.0/15 | 131k | AS2914NTT America, Inc. | 76/76 |
More specific announcements
Nothing inside this block is announced separately.
Sibling prefixes
| Prefix | Addresses | Origin | Visibility |
|---|---|---|---|
| 207.56.13.0/24 | 256 | AS18186Nebula Global LLC | 76/76 |
History
- AS1818630th 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 207.56.12.0/24 in the calculator/24 reference
Routing data derived from RouteViews MRT archives and public registry data.