31.58.250.0/24

Currently announced by AS213799 CONHOST BILGI TEKNOLOJILERI VERI MERKEZI HIZMETLERI VE DANISMANLIK LIMITED SIRKETI, in the routed prefix 31.58.250.0/24.

Current ASN: AS213799; CONHOST BILGI TEKNOLOJILERI VERI MERKEZI HIZMETLERI VE DANISMANLIK LIMITED SIRKETI
Routed prefix: 31.58.250.0/24; Most specific route covering this prefix
ASNs over time: 2; 2 announcement records
RIR allocation: RIPENCC; United Arab Emirates · 31.56.0.0/14

Routing data · Nov 10, 2026, 12:25 UTC

ASN historyEvery routed prefix covering 31.58.250.0/24

Prefix	ASN	Name	Registered country	First seen (UTC)	Last seen (UTC)	Status
31.58.250.0/24	AS213799	CONHOST BILGI TEKNOLOJILERI VERI MERKEZI HIZMETLERI VE DANISMANLIK LIMITED SIRKETI	Türkiye	Before monitoring	2026-11-10 12:25	Announcing
31.58.250.0/24	AS219521	VERSADC	Türkiye	2026-11-08 10:25	2026-11-08 12:23	Stopped

More specific routes0 total

No more specific routes inside this prefix.

Change logAll changes

Detected (UTC)	Prefix	Change	ASN	Name	Previous ASN	Country
2026-11-08 10:25	31.58.250.0/24	Origin addedNo longer announced	AS219521	VERSADC	AS213799	Türkiye

Look up another address

RIR allocation record

Registry: RIPENCC
Allocated block: 31.56.0.0/14
Country: United Arab Emirates
Allocation date: 2011-01-28
Status: allocated

From the RIRs’ delegated statistics files. Shows where the addresses are registered, not where they are used.

How monitoring works

Every 2 hours ASNBase takes the bgp.tools global routing table (prefix → origin ASN) and compares it with the previous one. The detected time is the time of that comparison; the actual change can be up to about 2 hours earlier.
Only routes seen by more than 100 bgp.tools peers are listed as changes; routes with less visibility are only kept in the history.
A new announcement counts only if it is still in the next routing table, and a withdrawal only if the prefix is missing from two tables in a row, so short flaps are ignored.
ASNBase has been monitoring since 2026-10-19. “Before monitoring” under “First seen” means the route was already announced when monitoring started; the earlier date is unknown.
Prefixes first seen during the first day of monitoring do not count as new announcements: most of them were simply missing from the table at the moment monitoring started.
Countries and regions follow the ASN’s registration, not the actual location of the IP addresses.