Sancfil Technologies Internet Services: PeeringDB fix list
AS141514 · peeringdb.com/net/29468
3 things to fix in Sancfil Technologies Internet Services's PeeringDB record, from what its exchanges publish: 1 to add, 2 to correct. As of 2026-10-08 21:35 UTC.
Make the changes on Sancfil Technologies Internet Services's PeeringDB page: sign in, choose Edit, and find the exchanges under Public Peering Exchange Points. Speeds go in as megabits per second.
Add these exchanges (1)
On the exchange's own member list, but not in Sancfil Technologies Internet Services's PeeringDB record. Add one entry per connection with these values.
-
IPv4 223.31.200.173 IPv6 2001:e48:44:100b:a500:14:1514:1 Speed 10000 Mbps (10G) RS peer Yes PeeringDB's IX-F import is on for this exchange, so PeeringDB also suggests this change on the network's PeeringDB page.
Correct these entries (2)
Addresses or port speeds in PeeringDB that differ from the exchange's IX-F export. The changes below follow the export; if the export is the one that's wrong, tell the exchange instead.
-
Problem PeeringDB has The export has IPv4 address in PeeringDB, not in the export 103.27.171.245 none IPv6 address in PeeringDB, not in the export 2401:7500:fff6::19a none Port speed differs 40G 10G - The entry with IPv4 103.27.171.245, IPv6 2401:7500:fff6::19a isn't in the export: delete it if that connection is gone.
-
Problem PeeringDB has The export has Port speed differs 10G 100G - In the entry with IPv4 103.77.109.7: set Speed to 100000 (100G) (now 10000).
PeeringDB's IX-F import is on for this exchange, so PeeringDB also suggests this change on the network's PeeringDB page.
From ixreport.com/net/141514/: PeeringDB against each exchange's IX-F export and website members list. Exchanges whose lists couldn't be read on this update aren't included.