bgpreport

Network · data from 2026-11-12

AS18113 PFIZER-SG-AP - Pfizer Pte Ltd Singapore dual homed

Registry name: PFIZER-SG-AP - Pfizer Pte Ltd Singapore dual homed, SG · not in PeeringDB

6IPv4 routes 0.0% RPKI valid · 100.0% with a route object
0IPv6 routes
0RPKI invalid 0 origin · 0 maxLength
6No ROA 0 with no route object for this origin
0Low visibility seen by under 10% of full-table peers
6Route objects not announced registered with origin AS18113, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS18113, 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.
146.240.4.0/24 No ROA Other IRR onlyRADB 671 100% 67
204.114.196.0/23 No ROA Other IRR onlyNTTCOM, RADB 671 100% 67
204.114.196.0/24 No ROA Other IRR onlyNTTCOM, RADB 671 100% 67
204.114.220.0/24 No ROA Other IRR onlyNTTCOM, RADB 671 100% 67
204.114.221.0/24 No ROA Other IRR onlyNTTCOM, RADB 671 100% 67
204.114.250.0/23 No ROA Other IRR onlyNTTCOM, RADB 671 100% 67

AS-SET

AS18113 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 18 are in fix.csv.

  • ROA: none6
  • Route object: RIR6
  • Route object: not announced6
ChangePrefix or setDetailFull-table peers
ROA: none146.240.4.0/24No ROA covers it. Add a ROA for AS18113, maxLength 24.671 of 673
Route object: RIR146.240.4.0/24Route object only in RADB. Add it in the RIR database for the space.671 of 673
ROA: none204.114.196.0/23No ROA covers it. Add a ROA for AS18113, maxLength 23.671 of 673
Route object: RIR204.114.196.0/23Route object only in NTTCOM, RADB. Add it in the RIR database for the space.671 of 673
ROA: none204.114.196.0/24No ROA covers it. Add a ROA for AS18113, maxLength 24.671 of 673
Route object: RIR204.114.196.0/24Route object only in NTTCOM, RADB. Add it in the RIR database for the space.671 of 673
ROA: none204.114.220.0/24No ROA covers it. Add a ROA for AS18113, maxLength 24.671 of 673
Route object: RIR204.114.220.0/24Route object only in NTTCOM, RADB. Add it in the RIR database for the space.671 of 673
ROA: none204.114.221.0/24No ROA covers it. Add a ROA for AS18113, maxLength 24.671 of 673
Route object: RIR204.114.221.0/24Route object only in NTTCOM, RADB. Add it in the RIR database for the space.671 of 673
ROA: none204.114.250.0/23No ROA covers it. Add a ROA for AS18113, maxLength 23.671 of 673
Route object: RIR204.114.250.0/23Route object only in NTTCOM, RADB. Add it in the RIR database for the space.671 of 673

Route objects not announced

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

204.114.192.0/19RADBNo ROA
204.114.197.0/24NTTCOM, RADBNo ROA
204.114.198.0/23RADBNo ROA
204.114.198.0/24NTTCOM, RADBNo ROA
204.114.199.0/24RADBNo ROA
204.114.252.0/22NTTCOM, RADBNo 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.