5.10.249.0/24
At a glance
Addresses
/24 block
Visibility
80 of 80 vantage points
RPKI
Registry
AZAllocated 2nd May 2012
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 AS212607seen on 400 paths from 80 vantage points
- Peer of AS31549seen on 9,600 paths from 80 vantage points
- Peer of AS205647seen on 15,113 paths from 80 vantage points
- Peer of AS49666seen on 74,980 paths from 142 vantage points
- Peer of AS6762seen on 204,619 paths from 43 vantage points
- Peer of AS3356seen on 997,311 paths from 2 vantage points
IR
IT
US
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
- London, UK2126073154920564749666551112998529This path
- Sao Paulo212607315492056474966667623356266213Shown above
- Singapore2126073154920564749666123894766132337This path
- Oregon, US21260731549205647496666762693920130This path
- Amsterdam2126073154920564749666676217434549213151This 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
- RIPE NCC — Europe, Middle East, Central Asia
- Country
- Azerbaijan
- Allocated
- 2nd May 2012
- Allocation block
- 5.10.240.0/20
- 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 |
|---|---|---|
| 5.10.249.0/24 | AS212607 | /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 |
|---|---|---|---|
| 5.10.248.0/24 | 256 | AS212607Saeid Shahrokhi | 80/80 |
History
- AS21260712th 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 5.10.249.0/24 in the calculator/24 reference
Routing data derived from RouteViews MRT archives and public registry data.