Possible reissue candidate; not confirmed available.
Timeline (3)
Every change the tracker has found, newest first. It covers ARIN from 2008-12-01, the RIPE NCC from 2010-04-23, APNIC from 2008-02-15, LACNIC from 2012-06-29 and AFRINIC from 2012-10-03.
2026-10-19RIPE NCC− DeregisteredRemoved (return, revocation or reclamation not publicly distinguishable)Strong inference
Statistics
AS198182 allocated on 2026-10-18, reserved on 2026-10-19
Inventory
Possible future reissue candidate after hold
Hold estimate
Estimated hold end 2027-04-17. Possible reissue candidate after this date; not confirmed available.
Removed from active registration. The tracker found it by comparing the RIPE NCC's daily statistics. The RIPE NCC's statistics show it allocated (dated 2011-10-28) on 2026-10-18 and reserved on 2026-10-19. Public sources do not distinguish a voluntary return, revocation, or reclamation. The RIPE NCC holds returned, revoked and reclaimed ASNs for 180 days (six months), or longer while still routed, before reissuing them, so the estimated hold end is 2027-04-17. This does not confirm availability.
Evidence (3) · classifier 1.4.0,
StatisticsFound by comparing the RIPE NCC's daily statistics: AS198182 allocated on 2026-10-18, reserved on 2026-10-19source · retrieved
BeforeRIPE NCC delegated statistics 2026-10-18 (produced 2026-10-18T21:59:59+00:00), before the change: allocated (dated 2011-10-28)source · retrieved
AfterRIPE NCC delegated statistics 2026-10-19 (produced 2026-10-19T21:59:59+00:00), after the change: reservedsource · retrieved
The RIPE NCC's transfer log records a transfer from Vladivostok Telecom Ltd. (RIPE NCC) to SP Sbezhnev (RIPE NCC) on 2020-12-28 19:00 UTC. The registration changed hands; it is not a new allocation from the RIPE NCC.
Evidence (3) · classifier 1.4.0,
Transfer logTransfer log: RESOURCE_TRANSFER on 2020-12-28 19:00 UTC, Vladivostok Telecom Ltd. (RIPE NCC) to SP Sbezhnev (RIPE NCC); resources moved: AS198182source · retrieved
BeforeRIPE NCC delegated statistics 2020-12-27 (produced 2020-12-27T22:59:00+00:00), before the change: allocated (dated 2011-10-28)source · retrieved
AfterRIPE NCC delegated statistics 2020-12-28 (produced 2020-12-28T22:59:00+00:00), after the change: allocated (dated 2011-10-28)source · retrieved
Classification history for this change (4 versions)
: Intra-RIPE NCC transfer, confirmed (classifier 1.4.0) current
2011-10-28RIPE NCC+ RegisteredApparent new issuanceStrong inference
Statistics
AS198182 available on 2011-10-27, allocated on 2011-10-28
Inventory
Likely issued from RIPE NCC-controlled inventory
No transfer record matches. The RIPE NCC's statistics show it available on 2011-10-27 and allocated (dated 2011-10-28) on 2011-10-28. It moved from the RIPE NCC's unissued pool to an active registration dated around that day, so it appears to be newly issued by the RIPE NCC.
Evidence (3) · classifier 1.4.0,
StatisticsFound by comparing the RIPE NCC's daily statistics: AS198182 available on 2011-10-27, allocated on 2011-10-28source · retrieved
BeforeRIPE NCC delegated statistics 2011-10-27 (produced 2011-10-27T21:59:59+00:00), before the change: availablesource · retrieved
AfterRIPE NCC delegated statistics 2011-10-28 (produced 2011-10-28T21:59:59+00:00), after the change: allocated (dated 2011-10-28)source · retrieved
Classification history for this change (4 versions)
: Apparent new issuance, strong inference (classifier 1.3.0)
: Apparent new issuance, strong inference (classifier 1.3.1)
: Apparent new issuance, strong inference (classifier 1.3.2)
: Apparent new issuance, strong inference (classifier 1.4.0) current
Transfer records (1)
Date (UTC)
Log
Type
Range moved
From
To
RIPE NCC
Resource transfer
AS198182
Vladivostok Telecom Ltd. RIPE NCC
SP Sbezhnev RIPE NCC
Every record in the ARIN, RIPE NCC, APNIC, LACNIC and AFRINIC transfer logs that moved any part of this ASN (ARIN's from 2009, the RIPE NCC's from 2012, APNIC's from 2010, LACNIC's from 2016, AFRINIC's from 2018). A transfer between two registries is in both logs.
RDAP lookups
Looked up
Why
Registry
Handle
Organization
Status
Last changed
After 7 days
not registered (RDAP 404)
After 24 hours
not registered (RDAP 404)
First seen
not registered (RDAP 404)
Organization-level details only; contact details are never kept. RDAP shows the registration when it was looked up, not in the past.