subnet.im

45.234.167.0/24

At a glance

Addresses

256

/24 block

Visibility

99%

79 of 80 vantage points

RPKI

No ROA

Registry

LACNICTT

Allocated 29th April 2018

AS paths to this prefix

All paths

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

OriginVantage point · Singapore
One AS path to 45.234.167.0/24 as seen from Singapore, read outward from the origin: AS266792 → AS27789 → AS27665 → AS23520 → AS1299 → AS132337. Each hop is listed with its network name beneath the graph.AS266792NOVO COMMUNICATIO…OriginAS27789GREENDOTAS27665Columbus Communic…AS23520Columbus Networks…AS1299Arelion (fka. Tel…AS132337Axclusive

Seen from Singapore

  1. Peer of AS266792seen on 158 paths from 79 vantage points
  2. Peer of AS27789seen on 2,906 paths from 140 vantage points
  3. Peer of AS27665seen on 16,235 paths from 140 vantage points
  4. Peer of AS23520seen on 260,816 paths from 140 vantage points
  5. Peer of AS1299seen on 165,750 paths from 2 vantage points
  6. 6AS132337AxclusiveSGVantage 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. London, UK26679227789276652352012998529This path
  2. Singapore2667922778927665235201299132337Shown above
  3. Amsterdam26679227789276652352017434549213151This path
  4. Sao Paulo26679227789276652352012993356266213This path
  5. Oregon, US2667922778927665235206762693920130This 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

99%

Seen by 79 of 80 full-feed vantage points

Globally 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
LACNIC — Latin America and the Caribbean
Country
Trinidad & Tobago
Allocated
29th April 2018
Allocation block
45.234.164.0/22
Status
allocated
Origin validation
No ROA

No ROA covers this prefix, so RPKI has nothing to say about it either way. This is still the common case for a large share of the routing table.

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

Prefixes of the same length sharing a parent block with 45.234.167.0/24
PrefixAddressesOriginVisibility
45.234.166.0/24256AS266792NOVO COMMUNICATIONS LIMITED79/80

History

  1. AS26679212th 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 45.234.167.0/24 in the calculator/24 reference

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