You know that feeling?

It's Sunday afternoon, and as the games progress, blood drains from your face.

Maybe it's a player you released or traded who is suddenly going off. Maybe it's a player you benched who is lighting it up, while the one you started has just fumbled for the second time and is heading to the bench. Or maybe it's a player who you said you "hated" on national TV, and now he has decided to have the game of his life. (That last one has a very narrow audience.)

Whatever the case, we've all had that feeling. That "oh no" feeling.

It happened again on Sunday. I went pale. Tingles went up my spine. I got a bad feeling in the pit of my stomach. "Oh no, " I thought. "Please, no ..."

I checked my computer, I checked my phone, I checked Twitter, looking for any sign of hope, of any inkling it might not be as bad as I feared.

I found none.

Our app had crashed.

I was among hundreds of ESPN employees who had spent the good part of August promoting our new app. I have spent the past decade of my life promoting ESPN's league manager product, telling everyone who would listen why they need to play fantasy football and that when they did, they needed to do it on ESPN.com.

It is promotion I am happy to do, not just because it is part of my job but because I truly believe it. I think the app is great. I have played in fantasy leagues hosted by all of our competitors. Much of it is personal preference, but yeah, I like us best. I know how much fantasy means to you, how consumed we all get by it and how most of us rely on technology to play it. We need it to work. All the time.

But when it's not working on game day? That's the worst. So on Sunday afternoon, my social media starts blowing up. (If you ever want to feel better about yourself, take a stroll through my Twitter mentions from that day.) Emails are pouring in. Texts are lighting up my phone. "Hey, what's wrong with the app? "How come I can't see my scores?" "Did you know they're talking about you guys on CNN?"

So many emotions run through me. I feel terrible for our tech team, the guys who worked so hard on this all summer. I feel terrible for our fans, who have trusted their fantasy teams and leagues with us and we have let them down, and I feel helpless. There's literally nothing I can do to help. Eventually, the issue gets fixed. We're down for about four hours, including the 4 p.m. ET game-locking window. The tech team then spends more time putting into place solutions for league managers to fix the issues the outage caused.

On Monday, we do our podcast, and there's some information we need to get out there about how to fix any issues that Sunday's outage caused, but I also feel that I want to apologize, so I do.

I am thankful for the many fans who reached out saying they accepted my apology, saying they understood that some things are beyond people's control and appreciated the efforts ESPN has made and continues to make to try to provide the best fantasy service out there while keeping the cost at exactly $0.

Others reached out with notes like this one (I've edited it for length):

Hi Matthew,

Yesterday was not the best of days for ESPN. Throughout the day, the ESPN fantasy football/sports twitter/facebook accounts were continuously copy-pasting the scenario at hand with no further detail.

I have logged into the app today to see your face as the thumbnail of a video of you apologizing on behalf of ESPN for the gaffe. I get it, traffic is at its heaviest on the first Sunday of every season and it's not easy, even for the worldwide leader in sport.

I appreciated the apology, but I found it was a bit unfair. Not the fact that the app/servers crashed. But the fact that they made you apologize on their behalf. I don't think it was fair for you to take the blame. Nor of ESPN to record you apologizing on a podcast (usually an audio platform) and share it as much as they can. I'm sure their stance of you being 'the face of ESPN fantasy football' is their reasoning, but I sure don't think that you should apologize for something you have (let's admit) nothing to do with. It's not that you do coding, or any app development (aside for maybe some suggestions here and there).

I guess this is my way of saying that you are doing a great job (even if others aren't) and to keep your chin up during this time.

A loyal fan, Jonathan, Montreal, Canada

I got many notes like this, Jonathan, and it meant the world to me. I really appreciate the note, but here's the thing. Yes, you are correct that I don't write code or do app development, but I look at it differently.

These are my guys. We are a team here. ESPN Fantasy is not any one person or app or platform. It is a collection of a lot of very talented, hardworking people who all have two things in common. They love fantasy sports, and they believe in our company's mission statement: To serve sports fans anytime, anywhere.

I cannot begin to tell you how many good things I have gotten credit for, or been able to experience, based on work that I had nothing to do with. Our product team, engineering team, research, publicity, ad sales, marketing, programming, editorial or everyone else who has a hand in our success, all of them work their butts off, all of them are doing great work, and none of them need me.

So yeah, if I am damn lucky enough (and that's the right word here: lucky) to stand with these men and women in the good times, you'd better believe I am standing with them in the bad. They are truly the best of the best, and you know what? On Sunday, all of us had a bad day.

But if you think I will bail on those guys now or try to step back or say I'm not a part of this, you're nuts. I stand with my team, through good and through bad, and I do so proudly. While all this was happening, there were lots of other disappointments to be felt. Adrian Peterson. Todd Gurley. Brandon Marshall. Dez Bryant. Coby Fleener. Gary Barnidge. You may have heard me rant about Mark Ingram.

As the app was fixed and normalcy returned, my Twitter and Facebook feeds turned to questions about those guys. Do we bail? Are we screwed?

And the answer, for me, was the same all weekend, be it ESPN Fantasy or the players you drafted early. No, man, I'm not bailing. These are my guys.

Last year in Week 1, Watson had three catches for 19 yards. He would finish the season as the eighth-highest-scoring tight end. The second-highest-scoring tight end in Week 1 last year, by the way, was Austin Seferian-Jenkins, who had that huge 110-yard, two-touchdown game in a blowout loss to the Titans, then managed two more touchdowns and 228 yards in six games before being done for the season.

Last year in Week 1, Peterson had 52 total yards and no touchdowns and was RB38 for the week. After Week 1 last year, Bishop Sankey sat fourth in running back scoring after going off in that same game. Sankey did not survive this season's round of final cuts.

If you jumped on the Bishop Sankey train after last season's 86-yard, two-TD Week 1 performance, we hope you jumped off soon thereafter. Photo by Greg McWilliams/Icon Sportswire

Last year in Week 1, Beckham went 5-for-44 and was tied for WR48 going into Week 2. After Week 1 last year, the fifth-best wide receiver in fantasy was, you guessed it, the Titans' Kendall Wright.

Don't let one game, one weekend, make you lose perspective. Yeah, Sunday was a bad day. No doubt. But better ones are ahead. So I am not panicking.

Quarterbacks I love in Week 2

Drew Brees, Saints: The second-leading scorer last week and first-ballot Hall of Famer may seem like an obvious name, but when I looked at my fellow co-rankers, I was the highest on him. Three of our five rankers have him outside the top three, two of whom have him outside the top five. I am aware of Brees' home/road splits, and yes, this game is outdoors in New Jersey. I am also aware of the improved Giants defense. But while their front line impressed me, I'm less sold on their secondary. Dez Bryant and Cole Beasley easily could have had scores against the Giants last week, and with the Saints' run game stymied a bit, expect Brees to exploit a Giants pass defense that is vulnerable inside. (Hello, Willie Snead!) I expect New York to have its way with the Saints' defense, and while I'm not saying it'll be a seven-touchdown shootout for Brees like last year, he is a must-start in season-long play and worthy of strong consideration in daily.

Eli Manning, Giants: We're all on Eli this week, especially at home. Last season, no quarterback threw more passes and had a higher touchdown-to-interception ratio at home last season than Eli. The Saints' defense is -- what is the word I am looking for? -- crappy. New Orleans gave up six different pass plays of 20-plus yards, and it won't get any better by Sunday.

Matthew Stafford, Lions: I mentioned this in my preseason 100 facts column, but the change in Stafford since Jim Bob Cooter took over is remarkable. It's probably gotten lost in all the jokes about his name, but Cooter took over midweek in Week 8 last season (on the way to a London game, no less). The Lions had their bye in Week 9, and Cooter got to make adjustments. From Week 10 last year through last week, here's the entire list of QBs with more fantasy points than Stafford during the past nine regular-season games:

Cam Newton and Russell Wilson.

That's it. That's the whole list. Only Wilson has more passing touchdowns, Stafford is sixth in passing yards since then, and no qualified QB has fewer interceptions. (He has only two since Week 10 last year.) Just so you understand what we are dealing with here, an elite fantasy quarterback who is still available in 20 percent of ESPN leagues. At home against a Titans team that doesn't have the personnel to keep up with the Lions' weapons, Stafford is an easy top-five play this week.

Others receiving votes: I know, he looked bad against the Steelers, but I like Kirk Cousins for a bounce-back against the Cowboys in a game featuring two suspect defenses. ... Joe Flacco is healthy and has some weapons and no running game. He's facing Cleveland? That'll work. ... Matt Ryan is the only QB to be a top-five fantasy QB in the first month in three of the past four seasons. On the road, yes, but the Falcons will struggle to run, and the Raiders don't have an answer for Julio Jones. Ryan will keep it going this week in a top-15 sort of way.

Quarterbacks I hate in Week 2

Russell Wilson attempted a career-high 43 passes in Week 1, but it's the health of his ankle this week that could limit the rushing stats that are so helpful in fantasy. Kirby Lee-USA TODAY Sports

Russell Wilson, Seahawks: If we see by Friday he is practicing fully and has no issues with his ankle, ignore this. But as of this writing, he's still a bit gimpy, which limits his mobility and, thus, his fantasy production. From 2012 to '15, no QB scored more fantasy points outside the pocket than Wilson. Weirdly, he hasn't been that great against the Rams (15 and 20 points in two meetings last season, which is solid but not otherworldly). Given how bad the Rams are this season, I can see Seattle's defense getting the Hawks up big and the team resting Wilson in the second half or just running a lot. If he's healthy, it'll be a different story, but as of now, I am concerned enough to be lower on him than normal.

Tyrod Taylor, Bills: He played against the Jets on short rest last season and finished with just 170 total yards. He'll have a banged-up Sammy Watkins or not have him at all. Taylor had just one passing score on his 55 pass attempts against the Jets last season. Taylor has not thrown a touchdown in three straight games, and there's only so much you can do with your legs. Ty-God will be back as a fantasy asset at some point this season, but I can't see him as a top-12 play this week.

Dak Prescott, Cowboys: Not unless you get points for handoffs. There will be no need for Prescott to attempt a pass in this one, as Ezekiel Elliott will run all over Washington. So if you saw Ben Roethlisberger on Monday night and think Prescott will carve up Washington like he did, think again and look elsewhere in deep leagues or if searching for cheap DFS plays.

Running backs I love in Week 2

Ezekiel Elliott, Cowboys: "Mama, who is that bad, bad man?" -- Me, curled in a ball crying as I watch this game, probably.

Latavius Murray, Raiders: A week after his team rushed for a league-high 167 yards, including an NFL-best 88 yards after contact, Murray gets a home game against a Falcons team that gave up 137 total yards and a score to Bucs running backs last week. Atlanta struggled in short yardage last season as well, giving up the second-most rushing touchdowns of 10 yards or fewer, and behind that Raiders offensive line, expect Murray to punch one in and run well to help set up play-action.

Jeremy Langford, Bears: He has scored in four of his five career games with at least 15 touches, and he's certainly going to get that much of a workload Monday night against an Eagles team that just gave up 137 total yards and a score to Browns running backs (5.6 yards per carry) in a game it controlled against a struggling offense. No defense gave up more yards per carry and more rushing attempts per game than the Eagles last season, as they ranked bottom-10 in both yards gained before first contact and yards gained after first contact. Langford is a legit top-15 play this week.

Rashad Jennings, Giants: I want as much of this game as I can get. In 11 of their past 17 games, the Saints have allowed 15-plus fantasy points to opposing RBs. The question with Jennings has never been talent; it has been health and opportunity. Well, he's healthy, and the Giants have picked up where they left off last season in terms of workload. Jennings is averaging 119.8 yards from scrimmage in his past five games, he's at home against the Saints, and on Sunday, he'll make it six solid fantasy efforts in a row.

Matthew Berry's RotoPass Need help with customized ranks for your scoring system, lineup setting tools, season-long projections and in-season trades? You need the Ultimate Fantasy Football resource. With RotoPass you get access to several leading fantasy football sites for one low price. You're welcome. -- Matthew Berry

Others receiving votes: I expect a split in carries in the Seahawks' backfield, but a gimpy Russell Wilson and a nice second-half lead against the Rams make both Thomas Rawls and Christine Michael viable flex plays this week. ... I've never been a huge T.J. Yeldon fan, but with no Chris Ivory again this week and a matchup with a San Diego team that looked, um, overmatched last week against Spencer Ware, I'm firing up Yeldon on Sunday. ... You already know how I feel about Stafford, so make no mistake, Theo Riddick's usage is legit, and his role in an elite pass game is secure. ... Chris Thompson is gonna be Theo Riddick lite this season, as the Redskins often play from behind, including this week, where they won't be able to run once again. I wouldn't expect a score, but he'll be a legit part of the passing game. ... Only five defenses allowed more RB receptions than the Raiders last season, so yeah, count me as in on the Tevin Coleman hype train. Notice I didn't mention Devonta Freeman at the top in terms of standing by our guys. He was a preseason "hate" for me, and Coleman is one of the reasons. He's still available in about 40 percent of ESPN.com leagues, too, don'tcha know?

Running backs I hate in Week 2

Melvin Gordon, Chargers: Lost in the two-touchdown game for Melvin is the fact that Danny Woodhead played twice as many snaps, had 21 touches compared to Gordon's 14 and, in fact, had more rushing attempts as well (16 to 14). With Keenan Allen out, every pass-catcher is going to have to be more involved and that includes Woodhead, who should fare better than Gordon against an improved Jags defense that last week held the Packers to just 3.8 yards per carry and was fifth-best in terms of yards per carry against last season.

Frank Gore, Colts: I swear, Gore is going to have value this year. A preseason favorite of mine because he was being drafted so crazy low and basically has the job to himself, he wasn't great in Week 1. Things look bleaker this week on the road against a Denver team that allowed a league-low 3.3 yards per rush last season, though. He did get 18 touches last week, and the Colts will need his blocking, so he will be on the field a lot if you're looking for a silver lining. But until there's improvement on the Colts' O-line, you'll need a touchdown from Gore to make him worthy of a start.

Ryan Mathews, Eagles: Mathews is averaging just 3.39 yards per carry in his past six games, so you'll need a touchdown and volume to make him work this week. To which you say, yeah, I know, so what's the issue? Well, the Bears actually possess a decent (not great, but not terrible, either) run defense, as they given up just nine rushing touchdowns since the start of last season. Yes, Lamar Miller had a huge day against them last week, but look closer. It took the Texans 35 carries to get to 129 rushing yards last week, just 3.7 yards per carry. I can't see the Eagles committing to the run like that, especially in a game they could easily be trailing. Not a top-20 play for me this week.

Wide receivers I love in Week 2

Brandon Marshall, Jets: Think he goes two bad games in a row? Yeah, neither do I.

Against a depleted Colts secondary, it's not too much to ask for Emmanuel Sanders to repeat his 6-catch, 90-yard, 1-TD performance against them from last season, is it? Mark J. Rebilas-USA TODAY Sports

Emmanuel Sanders, Broncos: With Demaryius Thomas banged up, Sanders will be the main beneficiary of going against that very exploitable Colts secondary. And with Denver running the ball so effectively, this sets up nicely to take some shots down the field to Sanders. Gut call, but I say he hits one.

Doug Baldwin, Seahawks: Eight catches for 118 yards and a score the last time these two teams met. The Rams don't have anyone who can keep up with Baldwin and, as mentioned, a hobbled Wilson will look to exploit quick matchups rather than run around and let deep plays develop. We saw Jeremy Kerley exploit the Rams from the slot on Monday night, and Baldwin is, shall we say, an upgrade over Kerley.

Willie Snead, Saints: You already know I love Brees in this matchup, and the underrated Snead should have another big week, too. You think about what Cole Beasley did to these Giants last week, and it's hard not to get excited about Snead, who played the majority of his snaps from the slot last week. Worth noting, in case you think Snead is a fluke:

Past 16 games for Willie Snead: 78 catches for 1,156 yards and 5 touchdowns

Jarvis Landry was WR15 last season with 1,159 yards and 4 touchdowns

Golden Tate and Marvin Jones, Lions: Calvin who? The only people who will enjoy this week's home matchup with the Tennessee Titans more than Tate and Jones are their owners.

Others receiving votes: It's not just chicks who dig the long ball; it's also Joe Flacco. Expect him to take a few shots and connect on at least one with Mike Wallace against the Browns on Sunday. ... You're already starting Odell Beckham Jr., but given the matchup (and their usage last week), Sterling Shepard and Victor Cruz are on the radar this week as well. ... A lot of people will have to step up for the Chargers now that Keenan Allen is lost for the season, and one of them should be Tyrell Williams, whom Philip Rivers has spoken highly of in the media. Definitely a risk/reward play at this point, but he's a name to consider for super-deep leagues or a GPP in daily.

Wide receivers I hate in Week 2

T.Y. Hilton, Colts: Because he'll likely draw Chris Harris most of the time, this is a tough spot for Hilton. Denver is tied for the fewest completions allowed on passes thrown 15-plus yards and ranks second in completion percentage allowed on such passes. Hilton doesn't have the size advantage that a Kelvin Benjamin does, and it's worth noting that he has scored a touchdown in just three of his past 22 games (including playoffs). After this weekend, it'll be three of his past 23 games.

Dez Bryant, Cowboys: Washington always plays him tough (six straight games versus the Redskins without more than five catches), and he has more than 50 receiving yards in just two of his past 10 games overall. There is no need for the Cowboys to get cute here; they will run the ball and do it successfully against the Skins, which means fewer shots to the end zone for Dez. He will need to score here to be worth the start, and the odds of that are not great.

Tight ends I love in Week 2

Gary Barnidge, Browns: Nowhere to go but up! Barnidge averaged more than 12 fantasy points per game last season when Josh McCown was the quarterback. (Last year's No. 1 tight end, Rob Gronkowski, averaged 11.7.) With McCown now starting in Cleveland, expect him to find Barnidge often. It's not a great matchup, but I'm putting him here because I know a lot of owners were burned by him last week (sheepishly raises hand). I'm back in this week, and you should be, too.

It's worth reminding that last season Delanie Walker had his two worst games, in terms of receiving yards, in his first three games played. Jim Brown-USA TODAY Sports

Delanie Walker, Titans: Another star who had a quiet Week 1 who I think gets back on track in Week 2 against a Lions team that just gave up three scores to tight ends last week. He's an easy top-four play for me this week and someone I would try to pry from an impatient owner. He won't be this cheap next Tuesday.

Others receiving votes: With Demaryius Thomas banged up, I could see some extra love going to Virgil Green, who has a nice matchup with the Colts. Indy coughed up five catches for 46 yards and a score last week to Eric Ebron. ... Jacob Tamme led the Falcons in catches and targets in Week 1, and certainly, despite what a Coby Fleener owner might tell you, the matchup with Oakland is solid. ... Speaking of that game, I also like Clive Walford to bounce back after last week's disappointment. The Falcons allowed five catches for 64 yards and two scores to tight ends last week.

Tight ends I hate in Week 2

Martellus Bennett, Patriots: There's a chance Gronkowski is back this week, and even if he's not, this isn't the best spot for Bennett to blow up. The Dolphins were top-10 versus tight ends last season, and there were nine games in which they allowed 30 or fewer yards to tight ends. I thought Miami's pass rush looked pretty good last week, so I could see Bennett having to stay in to block more this week. He's on the Patriots, so he has a chance to score at any time, but that's what you'll need to have him pay off this week as a top-10 option. If you think he'll score, start him. If not, look elsewhere.

Jimmy Graham, Seahawks: I'm trying to remember a quicker fall from fantasy superstar to afterthought than Graham, but either way, you're not starting him until you see something. And as discussed in the Russell Wilson section, that's unlikely this week. Especially until we see him fully healthy, as Graham played just 13 of 82 snaps last week.

Matthew Berry, The Talented Mr. Roto, is also standing by Kirk Cousins, though he admits that is shakier than it was last week. He is the creator of RotoPass.com, a paid spokesman for DraftKings.com and one of the owners of the Fantasy Life app.