Developers reported access problems with GitHub on Monday morning, according to outage-tracking service Downdetector, which recorded a spike in user complaints beginning at 9:45 a.m. EDT, though independent monitoring services offered a mixed picture of the platform’s overall operational status at the time.

Downdetector posted on its official account on the social platform X that “user reports indicate problems with GitHub since 9:45 AM EDT,” tagging the post with the hashtag #GithubDown and directing users to its outage-tracking page for further updates. The post had drawn nearly 1,900 views within a short period after being published.

GitHub, owned by Microsoft, serves as one of the world’s most widely used platforms for code hosting and collaborative software development, supporting workflows for millions of individual developers, open-source contributors and enterprise engineering teams globally. Any disruption to the platform’s core services, including code repositories, pull requests, authentication and continuous integration tools, can have immediate ripple effects across software development pipelines that depend on GitHub for day-to-day operations.

Independent status-tracking services showed varying assessments of GitHub’s health around the time of the reported issues. Entireweb Status indicated that GitHub was “operating normally” on Monday, noting the platform had received 79 user reports over the preceding 24 hours, with four of those submitted within the most recent hour before the check. UptimeRobot’s automated monitoring, which checks GitHub’s website every 10 minutes from infrastructure located in North America, reported that its most recent check prior to the disruption had not detected any unusual response times or error codes.

Other monitoring services similarly found no confirmed major outage as of their most recent checks. IsDown, which tracks GitHub’s official status page alongside user-submitted reports across 11 platform components, indicated it had received zero user reports in the 24 hours prior to a check conducted early Monday morning, though that check preceded the spike in complaints later reported by Downdetector. IncidentHub’s monitoring similarly described GitHub as “currently operational” as of a check conducted the prior day, while noting the platform had experienced 31 reported outages across 10 components over the preceding 30-day period, an indication of GitHub’s generally high, though not perfect, historical reliability.

GitHub’s own official status page, GitHubStatus.com, had two recently resolved incidents on record heading into this week. One involved a period of degraded availability affecting GitHub Actions, the platform’s workflow automation tool, on Aug. 6, during which workflow runs failed or remained queued for an extended period, affecting both GitHub-hosted and self-hosted automation runners. At the incident’s peak, 71% of workflow runs experienced infrastructure failures, while 75% of the remaining runs were delayed by more than five minutes, according to GitHub’s own incident report. The company said the disruption was triggered by a routine deployment to an internal service responsible for processing automation events, which exposed an existing capacity and concurrency weakness that caused a cascading failure across multiple internal clusters before engineers resolved the issue by expanding capacity and throttling incoming automated workloads.

A separate, smaller incident affected GitHub’s website on Aug. 10, when users were temporarily unable to create new fine-grained personal access tokens, a type of credential used to authenticate certain automated processes and third-party integrations. According to GitHub’s incident report, the issue stemmed from a change to how the website loaded certain front-end JavaScript code, which interfered with the token creation form’s confirmation step and prevented some users from successfully generating new tokens, though creating classic access tokens and editing or deleting existing fine-grained tokens remained unaffected throughout the incident.

GitHub’s most recently logged outage prior to Monday, according to outage-tracking service IsDown, occurred on Aug. 13 and was described as a “Disruption with GHEC Team Sync,” referring to an issue affecting GitHub Enterprise Cloud’s team synchronization functionality. IsDown’s tracking indicates the platform’s incidents typically resolve within roughly five hours on average, based on historical data compiled since the service began monitoring GitHub in April 2020.

As of this report, GitHub had not issued a public acknowledgment of the specific disruption reported by Downdetector users beginning at 9:45 a.m. EDT Monday, and the company’s official status page had not reflected an active, ongoing incident matching the timing of the reported user complaints as of the most recent available checks from third-party monitoring services.

GitHub has experienced various forms of service disruption throughout its history, ranging from routine deployment-related issues to more serious incidents involving distributed denial-of-service, or DDoS, attacks that have periodically taken the platform offline entirely for extended periods in past years. Such incidents have historically drawn significant attention given how deeply embedded GitHub has become in modern software development workflows, with many organizations relying on the platform not only for hosting their own source code but also for pulling external software dependencies and packages that other applications require to function.

Given the discrepancy between Downdetector’s reported spike in user complaints and the largely operational status reported by other independent monitoring tools around the same time, it remains possible that Monday’s reported issues reflected a more limited or regional disruption rather than a platform-wide outage, a pattern outage-tracking services note is common with brief or intermittent service issues that may affect certain user populations, geographic regions or specific platform components more than others.

Developers experiencing access issues were generally advised by outage-tracking resources to attempt accessing GitHub through an alternative browser, device or network, such as a mobile hotspot, and to check whether clearing a device’s DNS cache or temporarily disabling a VPN resolved the issue, steps commonly used to distinguish between a localized connectivity problem and a broader, platform-wide service disruption. As of this report, Downdetector’s tracking page for GitHub continued to collect user reports as the situation developed throughout the morning, and further updates were expected as GitHub’s engineering team, if an issue is confirmed, works to identify and resolve any underlying cause.

L3Harris Technologies said on Monday that CEO Christopher Kubasik stepped down from the role after an investigation by the board of directors found he engaged in misconduct, which led to the company reaching a separation agreement with him and naming his successor.

L3Harris’ announcement didn’t disclose the specific findings of the investigation, but said it “became aware of certain conduct that was not consistent with the values” outlined in the company’s code of conduct.

It noted that the conduct was unrelated to L3Harris’ financial reporting, controls, customer relationships or operational performance. The investigation was conducted with the assistance of outside counsel and prompted the board to determine that it was in the firm’s best interest to enter into a separation agreement with Kubasik.

L3Harris appointed Sam Mehta as its new CEO following the move. Mehta joined the company in 2023 and has 25 years of experience in the aerospace and defense industry, most recently serving as L3Harris’ president of space and mission systems (SMS) and communications and spectrum dominance (CSD).

TRUMP TURNS NATO SPENDING FIGHT INTO WIN FOR US DEFENSE COMPANIES

Chris Kubasik stepped down as CEO of L3Harris Technologies on Monday after a board investigation into code of conduct violations. (David Paul Morris/Bloomberg via Getty Images)

The SMS and CSD segments account for more than 80% of L3Harris’ total revenue, the company noted in its announcement.

L3Harris lead independent director Lewis Hay III was named chairman of the board and said that Mehta is a “proven executive who brings deep knowledge of our business, priorities and culture, making him ideally suited to become president and CEO at this important time in our company’s and our nation’s history.”

“Sam’s readiness to lead L3Harris reflects the Board’s robust succession planning and our focus on cultivating talent,” Hay added.

Mehta said in a statement that he is honored by the opportunity to lead L3Harris as its president and CEO, adding that he looks forward to working more closely with leaders and colleagues across the company to support the defense contractors’ mission.

“Today, L3Harris has a portfolio purpose-built for the future of warfare, and we are well-positioned to continue executing our focused growth strategy as The Trusted Disruptor,” Mehta said.

TRUMP’S RARE EARTH AGENDA HITS MILESTONE AS US ARMY MOVES TO BREAK CHINA’S GRIP ON DEFENSE METALS

Regarding Kubasik’s departure, Hay said that the departing executive had “overseen significant transformation during his tenure” and that the company appreciated his service, as they mutually agreed to implement the corporate succession plan.

L3Harris announced that Sam Mehta will now serve as CEO under the company’s succession plan. (Reuters/Brendan McDermid)

Reuters reported that under the separation agreement the company reached with Kubasik, the former CEO won’t receive severance payments, benefits or equity incentive awards. He will be permitted to retain and exercise previously vested stock options granted under L3Harris’ equity incentive plans, per the report.

DEPARTMENT OF WAR TAPS ORACLE FOR SOFTWARE DEAL WORTH NEARLY $7B

During his tenure at the company, Kubasik helped drive the 2019 merger of L3 and Harris Corp., serving as president and COO before he became CEO in 2021. The company acquired Aerojet Rocketdyne for $4.7 billion in 2023 as it expanded its presence in the defense sector.

In January, L3Harris announced the spin-off of its missile solutions unit, as the Pentagon said it would take a $1 billion stake in the new company. That spin-off was postponed last month until at least mid-2027.

GET FOX BUSINESS ON THE GO BY CLICKING HERE

Reuters contributed to this report.

This article was written by

Follow

So one of the political lessons of the primary election season is how badly polls have been wrong. Comrade Abdul El-Sayed in Michigan was supposed to win by more than 20 percentage points, but instead barely escaped by a thin cat’s whisker.

And the extremist Francesca Hong in Wisconsin was also supposed to win by 20 points or so. But she lost by an even thinner cat’s whisker.

And there are plenty of other examples. Where am I going with all this? Well, all these polls show President Trump’s supposed unpopularity on Iran or the economy or the much-abused term affordability may turn out to be very wrong in the midterm elections. 

Now, true enough, Mr. Trump’s not on the ballot, but I think when he really gets revved up on the campaign trail, and the GOP House and Senate people nationalize the election, we’re gonna find out that actual voters will reject big-government socialism and un-American values, as Newt Gingrich calls them.

Most of the recent polls don’t get likely voters. Instead they ask adults or registered voters and they’re frequently asking loaded questions. Now, one exception is my pal John McLaughlin, whose likely voter polls show that actually, people want Mr. Trump to finish Iran off. And additionally, a large majority prefers free market capitalism to socialism.

What’s more, the economy is doing far better than the mainstream press is telling us. Mr. Trump has always scored well with working class voters of all shapes and sizes. We are in a manufacturing boom. It is the strongest in years, probably decades.

Treasury Secretary Scott Bessent keeps telling people about the 105,000 hard goods producing jobs added this year alone. And since Mr. Trump came into office, the economy has produced 93,400 factory construction jobs. Think hard hats, think working folks.

Meanwhile, financial journalist John Carney reports that manufacturing wages have increased by nearly 5 percent so far this year. And that’s twice the inflation rate. 

On top of that, we’ve seen almost 400,000 federal jobs drop, and almost 900,000 private sector jobs created, which shows the Trumpian reconstruction of Biden’s big-government socialism.

Now, speaking of affordability and inflation, the democratic socialists love to talk about it. But it was under President Biden’s big-government socialism that the consumer price index cumulatively rose 21.4 percent during his four years.

Now, recently, even with the temporary bump up in energy prices from the Iran War, Mr. Trump’s new Federal Reserve chief, Kevin Warsh, has brought the inflation rate down to near zero in the last couple of months. And frankly, just over the past six months only 2.4 percent at an annual rate, which is nearly akin to the Fed’s 2 percent target.

Also, talking about affordability, Here’s one: Prescription drug prices have been plunging. Over the past year, they have declined 3.4 percent. And during Mr. Trump’s second term, they have not increased in any single month.

Now, these are just snippets of potential national messaging. Clearly, though, Mr. Trump’s free enterprise capitalism is powering a prosperous economy. And, hopefully, it will be buttressed with some middle class tax reform as part of the midterm election package.

Now, just as clearly, Democrats favor Medicare for All and huge tax increases and a state-run economy and open borders and defunding the police and defunding ICE and packing the Supreme Court and ending the Senate and other crazy notions that I think are gonna be very unpopular with real likely voters.

So don’t pay much attention to these early polls.

Some users reported difficulty accessing New York State’s official government website, ny.gov, though independent monitoring services largely showed the site functioning normally as of Monday, illustrating the kind of discrepancy that often accompanies isolated or intermittent online service disruptions.

Ny.gov serves as the central portal for New York State government, providing residents with access to a wide range of services, including applications for the Supplemental Nutrition Assistance Program, log-in access to NY.Gov ID accounts used across various state services, information on the Summer EBT food assistance program, and updates from statewide officials including Gov. Kathy Hochul, Comptroller Thomas P. DiNapoli and Attorney General Letitia James.

Independent status-checking services offered largely reassuring readings on the site’s operational status around the time reports emerged. IsItDownChecker, a third-party monitoring service, reported that ny.gov was “UP and responding normally” as of a check timestamped 11:02 a.m. GMT Monday, recording a response time of 179 milliseconds, an indicator generally consistent with normal server performance. The service noted that user reports of the site’s status were “at normal levels” at the time of the check, showing no clear evidence of a broader outage.

A separate check specifically targeting the New York State Department of Motor Vehicles website, a frequently used subdomain of the broader state government system, similarly showed normal operation. According to data compiled by outage-tracking service IsDownUS, automated checks conducted early Monday morning recorded consistent 200 HTTP status codes, the standard signal indicating a webpage loaded successfully, with response times ranging between roughly 1.8 and 1.9 milliseconds across multiple checks conducted between Aug. 15 and Aug. 17.

Despite those largely normal readings from automated monitoring tools, isolated user reports of access problems are not uncommon for large, heavily trafficked government websites, and such reports do not always indicate a site-wide outage. According to guidance published by IsItDownChecker, real disruptions affecting a website like ny.gov do not always present identically to every user, and can include several distinct patterns: server-side errors such as “502 Bad Gateway” or “503 Service Unavailable” messages, domain name system resolution failures that prevent a browser from locating the site at all, security certificate errors that cause a browser to block access even when the underlying site is functioning, or problems affecting only specific subsystems, such as a login portal failing while the rest of the site continues to operate normally.

The monitoring service also noted that when its own automated checks, which run from a centralized data center, are able to successfully reach a site, that generally indicates the disruption — if a user is experiencing one — may be limited to a specific internet service provider, geographic region or individual device rather than affecting the site broadly. In such cases, the service suggests potential fixes including switching to a different network connection, such as toggling between cellular data and Wi-Fi, changing a device’s DNS resolver settings, or testing access through a virtual private network connected to a different geographic region. If a problem persists only for an individual user despite the site functioning normally elsewhere, the guidance suggests the issue is more likely tied to a corrupted local DNS cache, an interfering browser extension, an outdated cached security certificate, or restrictions imposed by a corporate or institutional firewall.

New York State government systems have experienced significant, confirmed disruptions in the past, though none of comparable scale has been reported in connection with Monday’s user complaints. In July 2024, a widespread global technology outage tied to a faulty software update from cybersecurity firm CrowdStrike affected numerous systems both within New York State government and among private businesses across the state. Gov. Hochul addressed the incident directly at the time, seeking to reassure residents that the disruption did not stem from malicious activity. “The outage is having impacts here in New York for private sector businesses that rely on CrowdStrike, and for systems even within the New York State Government. I want to be very clear, at this time, we have no indication that this is a hack or a cyber security threat. It is more of a technical issue,” Hochul said at the time.

During that 2024 incident, state officials emphasized that emergency services, including 911 call centers, remained operational statewide despite the broader disruption, though several counties reported their internal computer systems had been affected. Hochul noted that backup systems allowed those affected jurisdictions to continue functioning despite the outage. “Our top priority is emergency services. We’re working with localities to ensure that 911 systems are operational. Multiple counties have notified our Office of Emergency Management that their internal computer systems have been impacted, and thankfully, all of them have backup systems for situations like this. New Yorkers in all 62 counties are able to call 911 at this time,” Hochul said.

Separately, the state’s DMV system has previously undergone planned service interruptions unrelated to any technical malfunction. In February, the department temporarily took all DMV applications offline for several days to implement a modernized technology system, according to a memo distributed to law enforcement agencies at the time. That planned outage, which ran from Friday afternoon through the following Wednesday, was designed to allow the department to test and launch new infrastructure rather than respond to an unplanned service failure.

As of this report, New York State officials had not issued any public statement acknowledging a confirmed, ongoing technical issue affecting ny.gov specifically in connection with Monday’s user reports, and the state’s official website continued to display standard service listings and public information, including recent press releases regarding electric vehicle charging infrastructure funding and upcoming state program deadlines, without any visible indication of a service disruption banner or maintenance notice.

Given the discrepancy between scattered individual user reports and the largely normal readings recorded by independent monitoring services, it remains possible that any issues experienced Monday were limited to specific users, regions or internet service providers rather than reflecting a broader outage affecting the site as a whole. Residents experiencing persistent difficulty accessing New York State’s official website or its associated services, such as the DMV portal or NY.Gov ID login system, were generally advised by monitoring services to attempt a full browser refresh, clear cached data and cookies, or try accessing the site from an alternative device or network before assuming a wider outage was underway.