All Systems Operational
AppVeyor CI   ? Operational
Build environment   ? Operational
NuGet.org   Operational
GitHub   Operational
BitBucket   Operational
VSTS   ? Operational
Operational
Degraded Performance
Partial Outage
Major Outage
Maintenance
Scheduled Maintenance
We are adding one more public IP address for AppVeyor build workers. If your build scenario includes communication (download or publishing) between AppVeyor build workers and private servers, you might need to update your firewall or router to allow traffic to/from 67.225.138.82.
Posted on Jan 11, 12:16 PST
Past Incidents
Jan 19, 2018

No incidents reported today.

Jan 18, 2018

No incidents reported.

Jan 17, 2018

No incidents reported.

Jan 16, 2018

No incidents reported.

Jan 15, 2018

No incidents reported.

Jan 14, 2018

No incidents reported.

Jan 13, 2018

No incidents reported.

Jan 12, 2018

No incidents reported.

Jan 11, 2018

No incidents reported.

Jan 10, 2018

No incidents reported.

Jan 9, 2018

No incidents reported.

Jan 8, 2018

No incidents reported.

Jan 7, 2018
Completed - The scheduled maintenance has been completed.
Jan 7, 21:13 PST
Scheduled - In connection with recently discovered Meltdown-Spectre bug in modern processors we are going to install emergency fix KB4056890 (https://support.microsoft.com/en-us/help/4056890/windows-10-update-kb4056890) on Hyper-V machines running customer builds and some infrastructure components. During this update some VMs will be switched to an alternative router with public IP 67.225.138.82 - make sure this IP is allowed on your firewall if you have IP restrictions applied. Full list of AppVeyor IPs can be found here: https://www.appveyor.com/docs/build-environment/#ip-addresses

Thank you for your patience!
Jan 7, 10:36 PST
Jan 6, 2018

No incidents reported.

Jan 5, 2018

No incidents reported.