bgpreport

Network · data from 2026-11-12

AS9890 ATOSINFOTECH-SG-AP - ATOS Information Technology (Singapore) Pte Ltd

Registry name: ATOSINFOTECH-SG-AP - ATOS Information Technology (Singapore) Pte Ltd, SG · not in PeeringDB

14IPv4 routes 21.4% RPKI valid · 92.9% with a route object
1IPv6 routes 0.0% RPKI valid · 0.0% with a route object
0RPKI invalid 0 origin · 0 maxLength
12No ROA 2 with no route object for this origin
1Low visibility seen by under 10% of full-table peers
24Route objects not announced registered with origin AS9890, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS9890, things to look at first. Visibility = full-table peers that see it, of 673 (IPv4) and 636 (IPv6) on 75 collectors. Also as routes.csv.

143.99.241.0/24 No ROA None 672 100% 67
2a00:ad87:4600::/48 No ROA None 632 99% 68
194.138.185.0/24 No ROA Other IRR onlyRADB 672 100% 67
203.95.64.0/22 No ROA Other IRR onlyRADB 672 100% 67
203.95.65.0/24 No ROA Other IRR onlyRADB 672 100% 67
203.95.66.0/24 No ROA Other IRR onlyRADB 672 100% 67
203.95.68.0/22 No ROA Other IRR onlyRADB 672 100% 67
203.95.70.0/24 No ROA Other IRR onlyRADB 672 100% 67
203.95.95.0/24 No ROA Other IRR onlyRADB 672 100% 67
194.138.244.0/24 No ROA RIR databaseRADB, RIPE 672 100% 67
203.95.80.0/20 No ROA RIR databaseAPNIC, RADB 672 100% 67
143.99.202.0/24 No ROA RIR databaseRIPE 670 100% 67
155.45.130.0/24 Valid Other IRR onlyRADB 2 0%low visibility 2
103.115.98.0/24 Valid RIR databaseAPNIC, RADB 672 100% 67
203.127.206.0/24 Valid RIR databaseAPNIC 671 100% 67

AS-SET

AS9890 isn't in PeeringDB, where networks name their AS-SET.

Fix list

The changes that would bring RPKI, the IRR and what's announced into line. Some are deliberate (a route object kept for a backup route, say); the network decides. All 46 are in fix.csv.

  • ROA: none12
  • Route object: none2
  • Route object: RIR8
  • Route object: not announced24
ChangePrefix or setDetailFull-table peers
ROA: none143.99.241.0/24No ROA covers it. Add a ROA for AS9890, maxLength 24.672 of 673
Route object: none143.99.241.0/24No route object for it. Add a route object with origin AS9890 in the RIR database for the space.672 of 673
ROA: none2a00:ad87:4600::/48No ROA covers it. Add a ROA for AS9890, maxLength 48.632 of 636
Route object: none2a00:ad87:4600::/48No route object for it. Add a route object with origin AS9890 in the RIR database for the space.632 of 636
ROA: none194.138.185.0/24No ROA covers it. Add a ROA for AS9890, maxLength 24.672 of 673
Route object: RIR194.138.185.0/24Route object only in RADB. Add it in the RIR database for the space.672 of 673
ROA: none203.95.64.0/22No ROA covers it. Add a ROA for AS9890, maxLength 22.672 of 673
Route object: RIR203.95.64.0/22Route object only in RADB. Add it in the RIR database for the space.672 of 673
ROA: none203.95.65.0/24No ROA covers it. Add a ROA for AS9890, maxLength 24.672 of 673
Route object: RIR203.95.65.0/24Route object only in RADB. Add it in the RIR database for the space.672 of 673
ROA: none203.95.66.0/24No ROA covers it. Add a ROA for AS9890, maxLength 24.672 of 673
Route object: RIR203.95.66.0/24Route object only in RADB. Add it in the RIR database for the space.672 of 673
ROA: none203.95.68.0/22No ROA covers it. Add a ROA for AS9890, maxLength 22.672 of 673
Route object: RIR203.95.68.0/22Route object only in RADB. Add it in the RIR database for the space.672 of 673
ROA: none203.95.70.0/24No ROA covers it. Add a ROA for AS9890, maxLength 24.672 of 673
Route object: RIR203.95.70.0/24Route object only in RADB. Add it in the RIR database for the space.672 of 673
ROA: none203.95.95.0/24No ROA covers it. Add a ROA for AS9890, maxLength 24.672 of 673
Route object: RIR203.95.95.0/24Route object only in RADB. Add it in the RIR database for the space.672 of 673
ROA: none194.138.244.0/24No ROA covers it. Add a ROA for AS9890, maxLength 24.672 of 673
ROA: none203.95.80.0/20No ROA covers it. Add a ROA for AS9890, maxLength 20.672 of 673
ROA: none143.99.202.0/24No ROA covers it. Add a ROA for AS9890, maxLength 24.670 of 673
Route object: RIR155.45.130.0/24Route object only in RADB. Add it in the RIR database for the space.2 of 673

Route objects not announced

Route objects with origin AS9890 whose prefix no peer sees AS9890 announce. Many are kept on purpose (backup routes, space announced only in some places).

85.238.140.0/22RADBNo ROA
185.75.231.0/24RADBNo ROA
193.221.90.0/24RIPENo ROA
194.138.240.0/22RADBNo ROA
203.95.64.0/24RADBNo ROA
203.95.67.0/24RADBNo ROA
203.95.68.0/24RADBNo ROA
203.95.69.0/24RADBNo ROA
203.95.71.0/24RADBNo ROA
203.95.80.0/24RADBNo ROA
203.95.81.0/24RADBNo ROA
203.95.82.0/24RADBNo ROA
203.95.83.0/24RADBNo ROA
203.95.84.0/24RADBNo ROA
203.95.85.0/24RADBNo ROA
203.95.86.0/24RADBNo ROA
203.95.87.0/24RADBNo ROA
203.95.88.0/24RADBNo ROA
203.95.89.0/24RADBNo ROA
203.95.90.0/24RADBNo ROA
203.95.91.0/24RADBNo ROA
203.95.92.0/24RADBNo ROA
203.95.93.0/24RADBNo ROA
203.95.94.0/24RADBNo ROA

Routes: the 08:00 UTC snapshots of 2026-11-12 from 75 RIPE RIS and RouteViews collectors. RPKI: our rpki-client run before the snapshot. IRR: the day's dumps of the five RIR databases and RADB's mirrors. The LEVEL3 and IDNIC databases publish no dump and aren't read, so route objects only there count as none.