192.33.14.0/24
Verisign Anycast SG 0DAS396729
Verisign Anycast JP 0EAS396605
Verisign Anycast CH 0AAS396761
Verisign Anycast FR 0CAS396707
Verisign Anycast BR 0EAS396659
Verisign Anycast IE 0AAS396653
Verisign Anycast US 2KAS396654
Verisign Anycast FI 0BAS396662
Verisign Anycast US 1QAS396583
Verisign Anycast AU 0AAS396738
Verisign Anycast NL 0BAS396614
Verisign Anycast US 2CAS396612
Verisign Anycast BG 0AAS396735
Verisign Anycast IN 0BAS396629
Verisign Anycast RU 0BAS396686
Verisign Anycast US 3DAS396702
Verisign Anycast NO 0AAS396704
Verisign Anycast US 3HAS396727
Verisign Anycast TZ 0AAS396646
Verisign Anycast PL 0AAS396751
Verisign Anycast CZ 0AAS396714
Verisign Anycast KW 0AAS396682
Verisign Anycast PT 0AAS396689
Verisign Anycast ZA 0BAS396675
Announced by more than one origin AS (MOAS).
At a glance
Addresses
/24 block
Visibility
10 of 80 vantage points
RPKI
Registry
USAllocated 30th November 2000
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 AS396659seen on 16 paths from 8 vantage points
- Peer of AS26415seen on 4 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
- Sao Paulo39665926415266213Shown above
- Singapore39672926415132337This path
- London, UK39668226415429618529This path
- Oregon, US39670226415693920130This path
- Amsterdam406477342129934549213151This 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
13%
Seen by 10 of 80 full-feed vantage points
Seen by few vantage pointsObserved at 1 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
- 30th November 2000
- Allocation block
- 192.33.14.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 |
|---|---|---|
| 192.33.14.0/24 | AS10515 | /24 |
| 192.33.14.0/24 | AS19836 | /24 |
| 192.33.14.0/24 | AS20172 | /24 |
| 192.33.14.0/24 | AS20362 | /24 |
| 192.33.14.0/24 | AS20431 | /24 |
| 192.33.14.0/24 | AS211369 | /24 |
| 192.33.14.0/24 | AS21313 | /24 |
| 192.33.14.0/24 | AS22547 | /24 |
| 192.33.14.0/24 | AS25485 | /24 |
| 192.33.14.0/24 | AS26415 | /24 |
| 192.33.14.0/24 | AS27544 | /24 |
| 192.33.14.0/24 | AS32651 | /24 |
| 192.33.14.0/24 | AS36616 | /24 |
| 192.33.14.0/24 | AS36617 | /24 |
| 192.33.14.0/24 | AS36618 | /24 |
| 192.33.14.0/24 | AS36619 | /24 |
| 192.33.14.0/24 | AS36620 | /24 |
| 192.33.14.0/24 | AS36621 | /24 |
| 192.33.14.0/24 | AS36622 | /24 |
| 192.33.14.0/24 | AS36623 | /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
No prefix of the same length in the same parent block is announced.
History
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 192.33.14.0/24 in the calculator/24 reference
Routing data derived from RouteViews MRT archives and public registry data.