subnet.im

207.56.226.0/24

JT TELECOM INTERNATIONAL PTE.LTD.AS137535

JT TELECOM INTERNATIONAL PTE.LTD.AS7607

Hong Kong Communications International Co., LimitedAS140227

Announced by more than one origin AS (MOAS).

At a glance

Addresses

256

/24 block

Visibility

63%

50 of 80 vantage points

RPKI

Valid

Registry

ARINUS

Allocated 16th February 1996

AS paths to this prefix

All paths

One observed path, hop by hop, from the origin out to Amsterdam.

OriginVantage point · Amsterdam
One AS path to 207.56.226.0/24 as seen from Amsterdam, read outward from the origin: AS137535 → AS400618 → AS140096 → AS9886 → AS2914 → AS34549 → AS213151. Each hop is listed with its network name beneath the graph.AS137535JT TELECOM INTERN…OriginAS400618Prime Security Co…AS140096JINX CO., LIMITEDAS9886CTCSCI TECH LIMIT…AS2914NTT America, Inc.AS34549meerfarbig GmbH &…AS213151Christian Elsen

Seen from Amsterdam

  1. 1AS137535JT TELECOM INTERNATIONAL PTE.LTD.SGOrigin
    Peer of AS137535seen on 2,951 paths from 80 vantage points
  2. 2AS400618Prime Security Corp.US
    Peer of AS400618seen on 9,303 paths from 142 vantage points
  3. 3AS140096JINX CO., LIMITEDHK
    Peer of AS140096seen on 9,788 paths from 142 vantage points
  4. 4AS9886CTCSCI TECH LIMITEDHK
    Peer of AS9886seen on 10,418 paths from 133 vantage points
  5. 5AS2914NTT America, Inc.US
    Peer of AS2914seen on 136,115 paths from 3 vantage points
  6. 6AS34549meerfarbig GmbH & Co. KGDE
    Peer of AS34549seen on 716,762 paths from 2 vantage points
  7. 7AS213151Christian ElsenDEVantage point

One 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

  1. Singapore1375358966132337This path
  2. Oregon, US7607693920130This path
  3. Amsterdam1375354006181400969886291434549213151Shown above
  4. London, UK1375354006181400969886291464538529This 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

63%

Seen by 50 of 80 full-feed vantage points

Partially propagated

Observed 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.

ROAs covering this prefix

Route Origin Authorisations covering 207.56.226.0/24
ROA prefixAuthorised originMax length
207.56.224.0/21AS137535/24
207.56.224.0/21AS140227/24
207.56.224.0/21AS153517/24
207.56.224.0/21AS395886/24
207.56.224.0/21AS40115/24
207.56.224.0/21AS7607/24
207.56.224.0/21AS8796/24
207.56.0.0/16AS140224/24
207.56.0.0/16AS18186/24
207.56.0.0/15AS2914/15

Prefix hierarchy

Announcements above, below and beside this one in the real routing table.

CoveringMore specific
Prefix hierarchy for 207.56.226.0/24: the announcements covering it on the left, the announcements inside it on the right. Every prefix drawn is also listed in the tables below.207.56.226.0/23AS137535207.56.226.0/23AS140227207.56.226.0/23AS7607207.56.0.0/16AS18186207.56.0.0/15AS2914207.56.227.0/24AS7607207.56.226.0/24AS137535This prefix207.56.227.0/24AS137535207.56.227.0/24AS140227

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.

More specific announcements

Nothing inside this block is announced separately.

Sibling prefixes

Prefixes of the same length sharing a parent block with 207.56.226.0/24
PrefixAddressesOriginVisibility
207.56.227.0/24256AS7607JT TELECOM INTERNATIONAL PTE.LTD.10/80
207.56.227.0/24256AS137535JT TELECOM INTERNATIONAL PTE.LTD.50/80
207.56.227.0/24256AS140227Hong Kong Communications International Co., Limited1/80

History

  1. AS760712th August 2026 — present
  2. AS13753512th August 2026 — present
  3. AS14022712th 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 207.56.226.0/24 in the calculator/24 reference

Routing data derived from RouteViews MRT archives and public registry data.