172.81.98.0/24
JT TELECOM INTERNATIONAL PTE.LTD.AS137535
JT TELECOM INTERNATIONAL PTE.LTD.AS7607
Announced by more than one origin AS (MOAS).
At a glance
Addresses
/24 block
Visibility
76 of 80 vantage points
RPKI
Registry
USAllocated 5th September 2023
AS paths to this prefix
All pathsOne observed path, hop by hop, from the origin out to Amsterdam.
Seen from Amsterdam
- Peer of AS137535seen on 2,951 paths from 80 vantage points
- Peer of AS400618seen on 9,303 paths from 142 vantage points
- Peer of AS140096seen on 9,788 paths from 142 vantage points
- Peer of AS9886seen on 10,418 paths from 133 vantage points
- Peer of AS2914seen on 136,115 paths from 3 vantage points
- Peer of AS34549seen on 716,762 paths from 2 vantage points
SG
HK
DEOne 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
- Singapore1375358966132337This path
- Oregon, US1375354006181400969886693920130This path
- Amsterdam1375354006181400969886291434549213151Shown above
- London, UK1375354006181400969886291412998529This path
- Sao Paulo137535400618140096988629143356266213This 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
95%
Seen by 76 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
- 5th September 2023
- Allocation block
- 172.81.96.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 |
|---|---|---|
| 172.81.96.0/22 | AS137535 | /24 |
| 172.81.96.0/22 | AS140224 | /24 |
| 172.81.96.0/22 | AS140227 | /24 |
| 172.81.96.0/22 | AS40115 | /24 |
| 172.81.96.0/22 | AS7607 | /22 |
| 172.81.96.0/20 | AS140227 | /20 |
| 172.81.96.0/20 | AS153517 | /24 |
| 172.81.96.0/20 | AS395886 | /20 |
| 172.81.96.0/20 | AS400618 | /24 |
| 172.81.96.0/20 | AS8796 | /20 |
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 |
|---|---|---|---|
| 172.81.99.0/24 | 256 | AS137535JT TELECOM INTERNATIONAL PTE.LTD. | 80/80 |
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 172.81.98.0/24 in the calculator/24 reference
Routing data derived from RouteViews MRT archives and public registry data.