subnet.im

188.214.60.0/24

At a glance

Addresses

256

/24 block

Visibility

5%

4 of 76 vantage points

RPKI

Invalid

Registry

RIPE NCCMD

Allocated 8th May 2009

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 188.214.60.0/24 as seen from Singapore, read outward from the origin: AS25198 → AS6204 → AS45899 → AS55329 → AS23673. Each hop is listed with its network name beneath the graph.AS25198INTERKVM HOST (Ze…OriginAS6204INTERKVM HOST SRLAS45899VNPT CorpAS55329Telcotech Ltd.AS23673Cogetel Online, C…

Seen from Singapore

  1. Peer of AS25198seen on 7,949 paths from 139 vantage points
  2. Peer of AS6204seen on 2 paths from 1 vantage point
  3. Peer of AS45899seen on 1,857 paths from 2 vantage points
  4. Peer of AS55329seen on 11,345 paths from 2 vantage points

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. Singapore251986204458995532923673Shown above

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.

Route visibility

5%

Seen by 4 of 76 full-feed vantage points

Seen by few vantage points

Observed 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
RIPE NCC — Europe, Middle East, Central Asia
Country
Moldova
Allocated
8th May 2009
Allocation block
188.214.60.0/22
Status
allocated
Origin validation
Invalid

A ROA covers this prefix but does not authorise this origin AS at this prefix length. That is either a misconfiguration or a hijack, and many networks will drop the route.

ROAs covering this prefix

Route Origin Authorisations covering 188.214.60.0/24
ROA prefixAuthorised originMax length
188.214.60.0/22AS213705/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

Prefixes of the same length sharing a parent block with 188.214.60.0/24
PrefixAddressesOriginVisibility
188.214.61.0/24256AS213705DIGITAL NETWORK S.R.L.75/76

History

  1. AS2519828th September 2026 — present
  2. AS21370522nd September 2026 — 6th October 2026
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 188.214.60.0/24 in the calculator/24 reference

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