199.7.70.0/24
At a glance
Addresses
/24 block
Visibility
80 of 80 vantage points
RPKI
Registry
USAllocated 20th March 2026
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 AS13335seen on 8,789 paths from 2 vantage points
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
- Amsterdam13335213151This path
- London, UK133358529This path
- Sao Paulo13335266213Shown above
- Singapore13335132337This path
- Oregon, US133352335220130This 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 80 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
- ARIN — North America
- Country
- United States
- Allocated
- 20th March 2026
- Allocation block
- 199.7.70.0/24
- Status
- allocated
- Origin validation
- Valid
A ROA exists that authorises this origin AS to announce this prefix at this length.
ROAs covering this prefix
| ROA prefix | Authorised origin | Max length |
|---|---|---|
| 199.7.70.0/24 | AS13335 | /24 |
Prefix hierarchy
Announcements above, below and beside this one in the real routing table.
Covering announcements
No less specific announcement covers this prefix.
More specific announcements
Nothing inside this block is announced separately.
Sibling prefixes
| Prefix | Addresses | Origin | Visibility |
|---|---|---|---|
| 199.7.71.0/24 | 256 | AS19836Verisign Anycast US 2M | 4/80 |
| 199.7.71.0/24 | 256 | AS20431Verisign Anycast US 3N | 2/80 |
| 199.7.71.0/24 | 256 | AS22547Verisign Anycast US 0A | 1/80 |
| 199.7.71.0/24 | 256 | AS36617Verisign Anycast US 0M | 1/80 |
| 199.7.71.0/24 | 256 | AS36623Verisign Anycast JP 0D | 1/80 |
| 199.7.71.0/24 | 256 | AS36631Verisign Anycast US 1A | 1/80 |
| 199.7.71.0/24 | 256 | AS40717Verisign Anycast GB 0J | 2/80 |
| 199.7.71.0/24 | 256 | AS211369Verisign Anycast FR 0E | 2/80 |
| 199.7.71.0/24 | 256 | AS396544Verisign Anycast US 0K | 3/80 |
| 199.7.71.0/24 | 256 | AS396545Verisign Anycast US 0L | 3/80 |
History
- AS1333512th 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 199.7.70.0/24 in the calculator/24 reference
Routing data derived from RouteViews MRT archives and public registry data.