Happy Saturday, all! Pull up a chair and join
me [mamu]for the fifth chapter in our ongoing series, The Complete History of Evolve. Read on to learn about
Adam'stransition from advisor to CEO, our first investment round, and the roaring return of the Evolve project. If you're new here, or just didn't feel like reading
last week's installment, here's the gist: although
dreijerand I had made some progress on Evolve, real life commitments and the LAN Bridger project pushed Evolve to the back burner. Adam came on board as an advisor. And the three of us finally met face-to-face for a few rounds of drinks at The Muddy Pig in Saint Paul, Minnesota.
• • • • •Adam Steps Up When we left off, it was
late 2008, and dreijer and I had invited Adam to join Echobit as an advisor. Although we had decided to temporarily shelve the Evolve project, we wanted to get a bit more serious about LAN Bridger, and Adam's previous business experience struck us as a great compliment to our grand, but perhaps naive, plans. The new year was upon us, and over the weeks that followed, it became clear that taking LAN Bridger to the next level would require more effort and discipline than dreijer and I had been pouring in to the project. Hamachi was becoming wildly popular, and LAN Bridger was still just a speck of dust on the radar compared to it. A few months in to
2009, we started bouncing around the idea of raising a small round of funding--enough to let dreijer and me start working for Echobit full time. Thoughts of Evolve also began to resurface. Perhaps we could raise enough funding to pursue them both? If we were going to get a lot more serious about Echobit as a company, and our two products, we realized Adam would need to be more than an advisor. Until this point, I'd been taking the liberty of calling myself Echobit's CEO, although doing so was born out of an idle amusement at job titles more than a clear background justifying the role. And so, in the early months of 2009, dreijer and I pitched Adam on becoming Echobit's CEO, and, effectively, our third partner and co-founder. As you may have guessed, he said yes, and has served as our CEO ever since.
• • • • •The Minnesota Cup & A Concept Trailer With Adam taking the business helm as CEO, we felt emboldened enough to dust off the crazy schemes we labeled Evolve, and see where they might take us. Together, the three of us hatched a plan to enter a local entrepreneurship contest, The Minnesota Cup. In exchange for submitting a detailed business plan, competing startups would receive critical feedback from regional business luminaries, exposure to the local investment ecosystem, and a chance at winning a not-insignificant amount of capital to help shore up operations. It was the perfect opportunity for Evolve! We officially entered the Cup on
31 May 2009, with just hours to spare before the deadline for the contest's first round. But would we advance to the next round?
Fun AsideWhile we waited with baited breath to hear back from the contest judges, Adam had conjured up an idea to make Evolve, still mostly words on paper, a bit more real to any potential investors, as well as the Minnesota Cup's judges. As Evolve was more than we could reasonably expect to launch without a bit of capital investment, why not simulate the product in the form of a concept trailer? We could whip up a script, and design something resembling an interface, cobble together some game footage--and combine these ingredients into a few minute explanation of the Evolve concept. We took the video idea over to the local production wizards at Fischer Edit, and over the summer, the team managed to produce
this awesome, if now a bit dated, concept trailer. The days continued to tick past, one by one, until
16 Jun 2009. Adam got the email first. We managed to beat out hundreds of other pitches, and made it as semi-finalists in the Minnesota Cup! Round two would prove a bit more elaborate than round one--to enter the Cup, we simply needed to put together what effectively amounted to an elevator pitch. To advance as semi-finalists, we needed to build a business plan, with explanations of how we would build our product, who our competitors were, and how we would make money. We submitted our 20 page business plan at the end of July, and played the waiting game once more... would we advance to the Minnesota Cup finals? Sadly, the answer came back in
Aug 2009: no, we would not. Our plan, even though it was accompanied by our snazzy concept trailer, had failed to convince the contest judges that Evolve would ever gain a significant number of users. Today, we're proud to say we have more than
370,000 reasonswhy those judges were wrong! Although we were a bit dejected from losing out on the Cup, we nevertheless opted to march on, and begin our search for investors in earnest.
• • • • •The First Investment As it turned out, that search wouldn't take much longer. Adam's penchant for pitching Evolve had only grown in the weeks following our participation in the Minnesota Cup, and by
Oct 2009, he'd managed to pull together a round of angel funding large enough to permit dreijer and me to start working on Evolve, as full time employees of Echobit! When Adam broke the news of our successful raise to us, we couldn't have been more ecstatic. We knew the road ahead would be a difficult one, but we finally had the opportunity to make Evolve a reality. My employment started in
Nov 2009, and dreijer scooted himself up from Kansas City, where he'd been working for the past year and change, in
Feb 2010. Onward and upward!
• • • • •Next Week... Tune in next week as The Complete History of Evolve puts the pedal to the medal, and dreijer, Adam, and I gear up to launch the private beta. What could possibly go wrong?
The weekend's in full swing, and by now, you ought know what that means! A new chapter in our ongoing series, The Complete History of Evolve. Read on to learn what happened to our first forays building Evolve, more about our future CEO, and the first time
myself [mamu]met face-to-face. If you haven't read
part 3 from last weekend, I'll recap the nitty gritty for you: dreijer and I had settled on a name for the successor to LAN Bridger, Evolve; dreijer took a stab at building Evolve for his senior university project; an old roommate and I looked in to building an Evolve Facebook app; and I met our future CEO at a local tech event.
• • • • •dreijer's Senior Project When we left off last weekend, it was
late 2007, and dreijer had come up with the excellent idea of using Evolve as fodder for his senior university project. The core concept we'd had in mind for Evolve involved a universal matchmaking engine. We wanted a tool that let you just log in, hit search, and boom, find a match--for any game (well, PC game) you wanted to play. By the mid-2000s, the cutting-edge of matchmaking engines were no longer simplistic free-for-alls. Algorithms like
Elo, originally devised for rating chess players, had been adapted for the madcap world of online gaming. For his project, dreijer had settled upon the idea of adapting an Elo-like rating algorithm for all games. After a match, anyone could rate players they'd met in the match, and the system would keep track of these ratings across all players and games. The ingredient that made it particularly clever involved bringing this rating mechanism in-game, but without developer assistance. We already knew we could get around the cruddy online-play modes many games included at the time--that was the entire basis of LAN Bridger. So dreijer began looking at ways to get his rating and matching interface injected in to games. Although overlay technology in 2007 was perhaps less exotic than in the few years previous, it still wasn't (and isn't) exactly straightforward. The basic idea dreijer conjured up involved hooking some of the internals of the games' rendering stack--only Direct3D for the scope of his university project--and adding textures representing his interface before the final image was sent out to a monitor. As spring 2008 rolled around, dreijer had made significant progress. His rudimentary matchmaking system could be brought up in a few different games, and while the skill-rating prompt had to be manually invoked (dreijer's code couldn't determine when a match had ended), it did the job. dreijer handed in his project to his university advisor, and waited for the evaluation--failure to pass would have thrown a wrench in dreijer's diploma. A few weeks later, the good news came: dreijer had passed! He had graduated from
DTUwith flying colors. In between all the madness surrounding his university project, dreijer had even managed to squeeze out another few updates for the still-nascent LAN Bridger.
Summer 2008came and went quickly for the now-graduated-and-job-hunting dreijer, and by fall, he'd decided to head to the States for a paid position with a tech company in the midwest. Exciting news, as this meant dreijer and I would finally be in the same time zone. Perhaps we could accelerate our big plans for Evolve!
• • • • •The Facebook App While dreijer was churning away on his university project, you may recall that an old roommate of mine,
Jeff, and I had started tinkering with a
Facebook app. The basic idea was to create a sub-profile within a Facebook profile, dedicated exclusively to gaming. Players would be able to rate games, add games to wish lists, and suggest games to their friends. If the app was to have any use, we knew we needed a reasonably large database of games to power it. But where to get such a database? We first thought about scraping
MobyGames, only to discover they require third-parties to license their data set. We emailed them to enquire about licensing opportunities for extremely early-stage companies such as ourselves, but heard nothing back. With MobyGames out of reach, we started looking for alternative ways to build the games database. After some brainstorming, we settled on scraping
Wikipediainstead. As it turned out, games on Wikipedia have a consistently structured sidebar with key information: names, genres, release dates, publishers, developers, and so on. We just needed to normalize the format of some of those pieces of data, and... Boom! Games database here we come! Jeff banged out the original parser in his free time--he and I were both seniors at Carleton College, ostensibly with course work to complete and senior projects of our own to finish--and before long, our games database had more than
10,000 entries, enough to make the Facebook app useful. I tuned the parser a bit more, and Jeff and I joined forces to build a rudimentary framework to power the backend Facebook's servers would hit when players used our app. We pushed the basic app out the door in
April 2008, and started roping our gaming friends in to using it to show off their gaming prowess. Over the next several weeks, we expanded functionality, eventually going so far as to include an in-app movie player with game trailers for popular and upcoming games.
• • • • •The Fate of All Things Our grand scheme was to eventually unite the Facebook app--or at least similar functionality like profiles, game ratings, and etc--and dreijer's senior project together under a unified Evolve banner. Unfortunately, life had a few other plans. Jeff wound up trekking around the world shortly after he graduated, and it became increasingly clear that the little Facebook app he and I built wasn't going to survive in the dog-eat-dog world of Superpokes, Graffitis, and so on--apps that racked up millions of users in the span on weeks. dreijer and I decided to terminate the Facebook app in the summer of 2008, and with dreijer getting ready to move to the US, and LAN Bridger starting to gain a small but dedicated following, we shelved his senior project, too, in favor of keeping LAN Bridger's momentum rolling in our precious little spare time. Thus, by
late summer 2008, Evolve had returned from whence it came. The ambitious plans dreijer and I had first laid out in those first fateful meetings in 2005 were effectively dead. How would Evolve ever come to life?
• • • • •Adam's New Startup By the
closing months of 2008, I'd gotten to know Adam much better, the result of collaborating with him on a new startup concept he'd been teasing out over the summer. Adam, if you recall from part 3, was the guy I met at a local tech event I'd attended in late 2007. The new startup Adam was ring leading involved building an online music platform similar to what Spotify, Rdio, and others would eventually bring to the market. Adam had brought together several acquaintances well-versed in everything from application design to marketing to programming, and was working out a game plan to get the ear of the record labels--something extremely critical to the startup's chances of success. Unfortunately, although the idea was an excellent one, the timing was a bit late. As 2008 marched to a close, one music streaming service after another was cropping up, many of which had already built up relationships with the music industry, in addition to being backed by large investment rounds. And so, in late 2008, with the music streaming startup a seeming impossibility, dreijer and I approached Adam with the idea of advising us in our endeavors with LAN Bridger. In
Oct 2008, after a pitch over lunch, and an introduction to dreijer via Skype, Adam graciously agreed to come on board and help us figure out how to turn Echobit in to a more serious venture--and perhaps resuscitate our ideas for Evolve!
• • • • •Face-to-Face-to-Face As the weeks rolled by, and 2008 finally drew to a close, a fortuitous circumstance arose. dreijer, who had settled in to his job in the midwest United States, had decided he'd spend his Christmas in the US rather than traveling the several thousand miles back to his homeland of
Denmark. I suggested dreijer come up to Minnesota to spend the 2008 holidays with my family--which meant flying to Minneapolis, crashing at my place there, and joining me for the multi-hour road trip to and from the northern wilds of
Minnesota. With Adam now on board as an advisor, and dreijer coming to Minnesota, we realized we really should seize the opportunity, and bond, face-to-face-to-face over a beer (or six)! And so, on
29 Dec 2008, after dreijer and I returned from the Christmas holiday up north, we joined Adam for a night at the fine Saint Paul drinking establishment known as the
Muddy Pig. Good times, and several delicious beers were had by all--hangovers, miraculously, kept to a minimum. To this day, Echobit is still made up of the three of us that had met at the Muddy Pig: dreijer, Adam, and myself.
• • • • •Next Week... Our little saga picks up the pace next week, with tales of our first investment, Adam's new role as our CEO, and renewed work on the tabled Evolve project. Until then!
Update 1 - 00:39 UTC Clients can once again log in to Evolve. It will take 30-45 minutes before all clients have managed to log back in. Hang in there while we're crushed under the awesome force of all of you hopping back online!
• • • • •Original Post A core Evolve server crashed a short while ago. We've rebooted it and are in the process of bringing up the rest of Evolve as we write this. Hang on a bit longer!
This release improves video recording, detection of Quick Sync on machines running Windows 8+, and works around recent issues with the detection of external broadcasting tools. Hooray! Read on for the full changelog.
• • • • •Full Changelog
- External broadcast detection has been updated to work around recent Twitch API changes. As a result, the client once again properly detects external broadcasting tools such as OBS and XSplit. Note that detection can take up to 2 minutes to kick in, depending on the load on the Twitch servers.
- Quick Sync feature detection for broadcasts has been improved for machines running Windows 8+.
- Fixed a crash if a broadcast was stopped and restarted in rapid succession.
- Fixed a crash if webcam was removed while a broadcast was stopping.
- Fixed a rare crash when joining a new party while already connected to a different party.
- Fixed an issue that caused a browser window to open when the client entered offline mode and the feed tab in the main window had been used.
- Fixed an issue that prevented video from being encoded for certain game resolutions.
It's another weekend, and time for another installment of the Complete History of Evolve. Read on to learn how LAN Bridger became Evolve, what exactly is in a name, and how we met our third co-founder. If you recall
part 2 from last weekend,
I [mamu]had decided to team up and turn
LAN Bridgerin to something more than just a summer project for dreijer's friends. Cue cheesy harp music, and a hazy fade to the year 2007.
• • • • •A Rose by Any Other Name... From the first few meetings dreijer and I had about LAN Bridger back in
2005, we'd had a vision for a product much more expansive than just a simple VPN. We wanted to build something with a social graph (friends, groups, etc.), profile pages, and with features that would cut down on the amount of time wasted trying to join a game with your friends. We wanted real-time chat, playtime tracking, and a way to make it easy to interact with our project when actually playing a game. We realized that our ambitions would be difficult to realize with just the two of us, so we focused on LAN Bridger solely as a VPN, whilst our grand plans for the future percolated in the backs of our minds. By the time the first beta version of LAN Bridger was gearing up for release in
late 2007, we'd settled on making our bigger vision an entirely separate project. All the sweet, sweet VPN goodness from LAN Bridger would carry over to this new project, of course, but we'd be able to more-or-less drop it in to the new thing and keep LAN Bridger running on its own. A new project meant coming up with a new name. LAN Bridger's name was born out of dreijer's simple, utilitarian aim for the project: it would bridge LANs. No need for anything fancy. But if the new project was going to be some grandiose vision for the future of gaming--hey, two university students could daydream, right?--it would need something a bit more imaginative. For weeks and weeks, from the end of the summer in to the
early fall of 2007, we mulled over a name for the new project, all the while calling it just
THE THING. A breakthrough came in the second week of
Sep 2007. dreijer and I were in the middle of one of our usual brainstorming Skype sessions when we started riffing again on a proper name for THE THING. Our minds started wandering to words associated with progress and change. Neither dreijer nor I can quite remember who was responsible, but out of one of our mouths sailed the word:
Evolve. Short. Simple. Bold. We loved it! But could we get a domain for it? Was it already used for something similar? Our first pick for a domain, www.evolve.com was already snapped up--held by the corporate behemoth known as Oracle. Once upon a time, it appeared it was used for some database product or another, but was, when we looked, simply redirecting to a generic sales page. Back to the drawing board, then. We started thinking about other popular apps and web apps at the time. Many of them used a simple formula for their domains: terms like app were appended to a generic word--voila, instant available domain name! We played around a bit more, until we settled on www.evolvehq.com. Still short and sweet, and easy to pronounce! We snapped up the domain on
14 Sept 2007, and have used it ever since. With our name and domain locked down, we were off to the races!
• • • • •Evolve Takes Form While we'd settled on the name and had a general idea for the direction we wanted to take Evolve, we had no idea where to begin. dreijer was still working on updates for LAN Bridger, and with the LAN Bridger and Echobit websites online, I was idling, looking for something to do. Earlier in 2007, Facebook had made its API available to web developers interested in building apps for the on-fire social network. Intrigued, I pitched dreijer on the idea of launching Evolve, at least initially, as an early Facebook app--a sort profile within a profile, loaded with the games you like and play, and a mechanism to discover others with similar tastes. We both decided it would be an interesting experiment, if nothing else, and I set off building the app with a roommate of mine at the time,
Jeff. As Jeff and I tinkered away, dreijer hatched the brilliant idea of developing some of Evolve's core tech as part of his senior project at DTU, his university. Specifically, he wanted to explore building a rudimentary skill-rating system, matchmaker, and in-game overlay. After running the idea by his advisor and getting a green light, dreijer dove headfirst in to the dark recesses of Direct3D hooking, matchmaking algorithms, and low-level Windows application development. In other words, the fun stuff!
• • • • •Adam, the Future CEO At the same time these twin explorations of Evolve were unfolding, I'd started participating in the Minnesota tech community, centered around the Twin Cities of
Saint Paul--a short drive north of where I was finishing my senior year of college. A demo showcase of nifty tech projects called
MinneDemowas slated for
mid-October 2007at O'Gara's Garage, a Saint Paul watering hole, and I decided it'd be a great way to meet various folks involved with the local startup scene. After the demos wound down, a mutual friend reeled me over to the bar, and introduced me to
Adam, a guy who'd just closed on the acquisition of his then-current startup. We shot the shit for the next 30 minutes, and as folks were beginning to leave, swapped contact info and agreed to stay in touch. A few days later, as dreijer and I were Skyping once more, I briefly mentioned the meet up at O'Garas, and this Adam character. We didn't know it at the time, but Adam would eventually become the third co-founder, and CEO of our little startup. That's it for this chapter in the saga of Evolve. Stay tuned next week to discover the fate of that early Facebook application, dreijer's senior project, more about Adam, and the first time all three of us met face-to-face.
Welcome to part 2 of our new blog series, The Complete History of Evolve! In this week's installment,
I'llbe recounting the story of
LAN Bridger, the predecessor to Evolve. When we
left off last week, I was hanging out with
dreijer, who was showing me a project he'd been working on over his summer, all the way back in 2005. That project, LAN Bridger, was built to let dreijer and his friends play LAN games over the internet.
• • • • •Why LAN Bridger? Some of you might wonder why dreijer and co. couldn't have just used a tool like
Tunngle. Turns out, those tools didn't exist yet! Hamachi was first released at the end of the summer in 2005, and Tunngle didn't arrive on the scene until 2008. Apart from the rather confusing and buggy
Gamer's Internet Tunnel, nothing else existed when dreijer started working on LAN Bridger.
• • • • •A Trial Run But back to the story. After I headed home from dreijer's, of course I had to play a few rounds of
Dungeon Keeper 2with
heland him over LAN Bridger--you know, for "testing" purposes. Ahem. And, to my amazement, LAN Bridger worked flawlessly! Rather than using EA's horrifically unreliable online lobby system for the game, we were able to skip straight to the LAN game list and hop in to a match immediately. A couple weeks later, as dreijer and I started talking more, I suggested that we should set up some kind of shared endeavor for LAN Bridger: he'd work on the software, and I'd work on an integrated website to make it easier to use. We met a few more times, and chatted frequently before I left Denmark--resulting in countless pages of ideas for LAN Bridger's future. Among those ideas: a friends list, chat rooms, and a matchmaking system to make it easier to find others to join games. As I returned to the States just before
Christmas 2005, both dreijer and I were determined to make LAN Bridger the best damn gaming utility we possibly could.
• • • • •LAN Bridger's Launch As he continued his studies, dreijer kept working on the LAN Bridger code throughout
early 2007. The original LAN Bridger concept involved a clever approach: it would capture the game's network packets, rewrite the packet headers, and forwarding them to whomever you were connected via a simple custom protocol. It worked well enough for many games, but didn't work at all for others. As a result, dreijer decided to scrap much of his original work on LAN Bridger, and rewrite it as a full-blown VPN instead. While dreijer was getting LAN Bridger ready for its public debut, I started, scrapped, and restarted several incarnations of the website, eventually coming up with the simple green-and-gray design that graces the LAN Bridger site today. By
summer 2007, just over two years from dreijer's first line of code, he and I were finally ready to launch LAN Bridger, version 0.9.0, to the world! Fame and glory were certainly awaiting us, right? Thousands and thousands of users, all ready to take us to the moon! Alas, no such luck. A few dozen of our friends gave it a whirl, and while they liked it, the world had no idea it even existed. dreijer and I weren't discouraged, however, and we resolved to keep improving LAN Bridger, and tell friends and friends of friends about it. As 2007 drew to a close, we had managed to release two significant updates to the software, including a basic interface to show connected peers, customizable IP ranges for the folks hosting virtual networks, and a few basic guides and troubleshooting pages for the LAN Bridger website. The improvements were enough to get a group of my friends,
dave, among others, to start regularly using the program to play the ever-popular
WarCraft III: The Frozen Throne.
• • • • •To Be Continued... If you're starting to think LAN Bridger sounds an awful lot like Evolve's
party system, you're spot on! Next week, as we continue the Complete History of Evolve, we'll take a look at how LAN Bridger transformed in to Evolve, the genesis of our overlay technology, and how dreijer and I met
adam, our CEO.
In the past week, we've added support for
14 new gameson Evolve. That brings the total count to
3,488 supported games! Thanks to everybody who spent the time to write and submit the rules. You guys rock! Here's the list of newly supported games:
- Titanfall submitted by HeavenNight
- Boson X submitted by CoolMan1342
- Roaming Fortress submitted by ThE_MarD
- The Grave Digger submitted by ThE_MarD
- Zombusters submitted by ThE_MarD
- 140 submitted by CoolMan1342
- Bit.Trip Fate submitted by CoolMan1342
- The Castle Doctrine submitted by Rekka
- Octodad: Dadliest Catch submitted by ThE_MarD
- 8bitMMO submitted by pacefalm
- Blackguards submitted by Aronstef
- Day One: Garry's Incident submitted by ThE_MarD
- Saviors submitted by ThE_MarD
- Survive submitted by ThE_MarD
Same $%~&, different day, right? At the risk of sounding like a broken record: we're being hit by yet another round of DDoS attacks. Clients should be coming back online at the moment, although whether future attack waves are inbound remains uncertain. Although this is quite frustrating for everyone (including us!), here's some good news. We've started talks with a potential partner for DDoS mitigation, and once we're further along, we'll be sharing the details.
Hi there! I'm
mamu, one of the co-founders of Evolve. Last week, we took you on a trip through
the highlights of 2013. This week, I'd like to invite you to hop in our hot tub time machine once again, as we kickoff our series on the complete history of Evolve. In part 1, we're dialing the year back to 2004: the year
dreijer--another Evolve co-founder--and I first met! Read the tale below, and make sure you stay tuned next weekend for part 2. We'll be talking about LAN Bridger, the project that got it all started!
• • • • •A Long Time Ago... In
2004, dreijer and I were both university students. Full of academic vigor. Or... was it beer? Can't quite remember. At any rate, dreijer was a software engineering major at the
Technical University of Denmark, and I was pretending to be a computer science major at
Carleton Collegein the United States. Neither of us had any clue the other existed. But not for long. As it turned out, dreijer and I shared a passion for adventure games--a bit of a niche genre by the time we were playing them, but still gems in our eyes. That passion led us both, in 2004, to join the forums at
Adventure Gamers, a great little fan site for the genre. And it wasn't terribly long after joining that we first crossed paths...
• • • • •A Fortuitous Meeting In
Dec 2004, using the handle
mst3k, I posted an oh-so-typically-naive request for advice on putting together a team on the internet to create a new adventure game. After a few helpful posts by the community, a mysterious
Hallokoarrived in the thread with sage advice on managing such a project, and recruiting others to it. It turned out he was running a project of his own. If you haven't guessed yet, Halloko was dreijer. We'd finally met, even if it was just online. Fast forward six months, to
summer's end 2005. I was getting ready to study abroad in a small country in northern Europe--dreijer's homeland,
Denmark. dreijer and I had fallen out of touch somewhat at this point, so I failed to mention anything about my travel plans until I was in the Danish capital, Copenhagen, for the start of term. One night, I noticed dreijer was online, and sent him a message: "Hey, you're somewhere around here! You're Dutch, right?" BZZT! WRONG! I'd done the stereotypical idiot-American thing and relocated my Danish friend two countries to the left from his actual home.
• • • • •dreijer's Summer Project Once we realized we were in the same country, of course we had to meet. I still remember hopping off the train in the sleepy town of
Birkerod, scanning the people milling about the station, trying to guess who dreijer was. I eventually spotted him, standing next to a very sweet collector MG--his pop's--and we zoomed off to his home. After a few rounds of sweet LAN games (his friend
helwas over, and demanded we try beat his supreme lair-construction skills in
Dungeon Keeper), dreijer decided to show me a project he'd been working on over his summer. I pulled up a chair, and he unveiled
LAN Bridger, a kick-ass little app that allowed dreijer and hel to play LAN games over the internet. You can probably guess where all this is heading...
Update 3 — 19:00 UTC; 8 Feb 2014 The attacks have subsided and our servers have been operating normally for the last several hours. We're still in talks with various folks to establish a long-term plan that lets us avoid outages when future attacks occur. Thanks again for your understanding and patience.
• • • • •Update 2 — 23:00 UTC; 7 Feb 2014 Unfortunately, we're being hit once again. Expect disconnections now and then, although, in general, there should not be a sustained outage this time. Also, for folks using the party system: keep in mind game traffic in parties is all peer-to-peer, so even if your client loses connectivity to our main servers, you should not experience an interruption in your current games. Do note that modifying parties (such as creating, joining, and inviting) doesn't work if you've lost the main Evolve connection.
• • • • •Update 1 — 16:00 UTC; 7 Feb 2014 Good news! Despite the attacks, we've managed to remain online over most of the night. We're actively discussing the attacks with the management at our ISP, in hopes of identifying a long-term solution that doesn't result in severe outages. Do let us know if you're still having trouble logging in with the client.
• • • • •Original Post Hey guys! As much as we hate to be posting this, we're under another round of DDoS attacks. We're working with our ISP to mitigate the attacks. We'll also be speaking with our ISP's management about their inability to deal with our situation--hopefully we'll have a long-term resolution in the works at some point in the near future. Hang in there just a bit longer.
About the Blog
You're reading the official Evolve blog. We regularly post details regarding upcoming features, game releases, changelogs, and an occasional comment about the industry. Make yourself at home!
- The Complete History of Evolve, Part 5 Posted 1 day ago by mamu
- The Complete History of Evolve, Part 4 Posted Mar 1 at 8:35pm by mamu
- Evolve Outage on 27 Feb 2013 Posted Feb 27 at 11:38pm by mamu
- Release: Evolve Client 1.8.3 Posted Feb 23 at 7:26pm by dreijer
- The Complete History of Evolve, Part 3 Posted Feb 22 at 11:44pm by mamu
- The Complete History of Evolve, Part 2 Posted Feb 17 at 3:19am by mamu
- Support for 14 New Games Posted Feb 16 at 8:01pm by dreijer
- DDoS Attacks on 10 Feb 2014 Posted Feb 11 at 2:25am by mamu
- The Complete History of Evolve, Part 1 Posted Feb 9 at 6:53am by mamu
- DDoS Attacks on 7-8 Feb 2014 Posted Feb 7 at 7:33am by mamu
- Expected Client Downtime on 6 Feb 2014 Posted Feb 5 at 6:54pm by mamu
- Release: Evolve Client 1.7.9 Posted Feb 5 at 4:09am by dreijer
- A Look Back at 2013 Posted Feb 1 at 11:56pm by mamu
- DDoS Attacks on 29-30 Jan 2014 Posted Jan 29 at 7:02pm by mamu
- Release: Evolve Client 1.7.8 Posted Jan 19 at 9:20pm by dreijer
- Release: Evolve Client 1.8.2 Posted Dec 19 '13 at 8:09pm by dreijer
- Release: Evolve Client 1.7.7 Posted Dec 16 '13 at 1:16am by dreijer
- Release: Evolve Client 1.7.6 Posted Dec 13 '13 at 7:04pm by dreijer
- Server Updates through Dec 8 2013 Posted Dec 11 '13 at 4:46am by mamu
- Release: Evolve Client 1.8.1 Posted Dec 9 '13 at 5:58pm by dreijer