April 2014 status report

All systems worked perfectly in April.

We pushed 75 software upgrades to our production systems.

Among them a new HTML5 based drag and drop upload module.
The previous version had a 2GB file size limit. The new one
has simply none. Which means that the entire INTERDUBS system
can now handle files of unlimited size.

This month the Heartbleed vulnerability was a big topic on
the Internet. We run our core systems with a conservative
feature set: We use established system software and patch
it for security issues if needed. Instead of just using the
‘latest greatest’ without a specific feature requirement.

We simply never saw the benefit of the OpenSSL Version 1.0.1
that was affected by this flaw.

This resulted in the pleasant fact that none of our
systems were ever impacted by this huge potential problem.

March 2014 status report

March saw perfect service records as well.

We upgraded the hardware in both our New York and Los Angeles data centers.

Even though our client base and usage data enjoys steadily increasing growth we are excited that both system load and site response times never have been better.

Technology is a good thing. We are happy to see that our considerable investments paid off so nicely.

February 2014 status report

Operations in February were smooth.

No troubles or outages of any kind.

January 2014 status report

During January no service interruptions or problems got in the way of our customers success.
Just like in 2013.

During January our software team pushed 107 updates into the running system.
As usual these improvements range from cosmetics to exciting new capabilities
and features.

December 2013 status report

INTERDUBS was running smoothly in all three data centers in December.

Looking at our growth and service records we are very happy with 2013.

In the full year there were no issues with the core services and only
two brief events caused by third parties impacted a small subset of our clients.
In both cases we were able to change operations / vendors so that future appearances
can be ruled out.

2013 exceeded our expectations, and we are looking forward to continue on this path.

We are aware that our success is entirely based on the quality of the relationship that
we enjoy with our clients. We are very thankful to be associated with such an awesome
group of collaborators.

November 2013 status report

As we are closing in on the 7 million file mark things ran smoothly in all data centers during November.

We extended the INTERUBS API functionality considerably.

October 2013 status report

None of the three INTERDUBS data centers experienced any problems in the October.

Uptime was 100%

Utilization reached 40% during peak times in our NY data center.
Per our internal policies this level of system use triggers an upgrade cycle of our resources.
We have installed new hardware that is currently being tested and should get deployed in the near future.

INTERDUBS runs update number 4,097 today.

September 2013 status report

Everything was working perfect in September 2013.

Currently we are running INTERDUBS update number 4,059.

The fact that there were no outages or glitches in September makes us especially happy since we did perform allot of restructuring work under the hood. It is always nice if these things go so smoothly that they do not impact daily operations.

August 2013 status report

All systems worked perfectly in August.

No outages – no glitches.

This is remarkable since we upgraded our network capacity again. The new gear appears to be working well and the transition was seamless.

As a general use we upgrade parts of the system if we peak use go above 25% of its total capacity.
Running things with this kind of over capacity ensures that no part of the system can become a bottleneck.

July 2013 status report

Things ran perfectly smooth in our three data center locations in July.

Unfortunately a DNS issue with our past DNS provider Network Solutions impacted services in the early morning hours of July 17th.

We since then have executed the change over to a new DNS provider that has a better track record in terms of reliability and performance.