This is standard practice. Its been said that best practice is to not share certs between servers, so you'll see different certificates from servers in different locations. From Verisign:
Can I secure multiple servers with a single certificate? Sharing
certificates on multiple servers increases risk of exposure. Auditing
becomes more complex, reducing accountability and control. If a
private key becomes compromised, it can be difficult to trace and all
servers sharing that certificate are at risk. Because sharing
certificates degrades security, the VeriSign certificate subscriber
agreement prohibits customers from using a certificate on more than
one physical server or device at a time, unless the customer has
purchased additional server licenses. VeriSign’s licensing policy
allows licensed certificates to be shared in the following
configurations: redundant server backups, server load balancing, and
SSL accelerators. See About SSL Certificate Licensing.
E.g., if I run
nslookup www.google.com on different computers I'll find several different IP addresses for different google servers.
One will give an SSL cert with a SHA256 fingerprint:
SHA-256: F6 41 C3 6C FE F4 9B C0 71 35 9E CF 88 EE D9 31 7B 73 8B 59 89 41 6A D4 01 72 0C 0A 4E 2E 63 52
while another will give:
SHA-256: 63 80 03 73 A7 74 72 E0 3E 7E 56 4E A2 17 2F C2 5C 37 D5 71 BD 05 10 1C B4 3C 14 00 04 92 0F 64
Both are "Builtin Object Token:Equifax Secure CA -> Google Internet Authority -> *.google.com" and appear to be valid.