bgpreport

Network · data from 2026-11-12

AS267145 Netsim Provedor de Sistema de Integracao A Midia

Registry name: AS267145 - Netsim Provedor de Sistema de Integracao A Midia L, BR · PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS267145, 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.
45.230.28.0/22 No ROA Other IRR onlyALTDB, RADB, TC 669 99% 67
45.230.28.0/23 No ROA Other IRR onlyTC 668 99% 67
45.230.28.0/24 No ROA Other IRR onlyRADB, TC 668 99% 67
2804:48cc::/33 Valid Nonecovered by 2804:48cc::/32 635 100% 67
45.230.30.0/23 Valid Other IRR onlyTC 669 99% 67
45.230.29.0/24 Valid Other IRR onlyTC 668 99% 67
45.230.30.0/24 Valid Other IRR onlyTC 668 99% 67
45.230.31.0/24 Valid Other IRR onlyRADB, TC 668 99% 67

AS-SET

AS267145's PeeringDB record names no 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 12 are in fix.csv.

  • ROA: none3
  • Route object: none1
  • Route object: RIR7
  • Route object: not announced1
ChangePrefix or setDetailFull-table peers
ROA: none45.230.28.0/22No ROA covers it. Add a ROA for AS267145, maxLength 22.669 of 673
Route object: RIR45.230.28.0/22Route object only in ALTDB, RADB, TC. Add it in the RIR database for the space.669 of 673
ROA: none45.230.28.0/23No ROA covers it. Add a ROA for AS267145, maxLength 23.668 of 673
Route object: RIR45.230.28.0/23Route object only in TC. Add it in the RIR database for the space.668 of 673
ROA: none45.230.28.0/24No ROA covers it. Add a ROA for AS267145, maxLength 24.668 of 673
Route object: RIR45.230.28.0/24Route object only in RADB, TC. Add it in the RIR database for the space.668 of 673
Route object: none2804:48cc::/33No route object for it. A route object for 2804:48cc::/32 with origin AS267145 covers it (filters allowing more-specifics accept it). Add a route object with origin AS267145 in the RIR database for the space.635 of 636
Route object: RIR45.230.30.0/23Route object only in TC. Add it in the RIR database for the space.669 of 673
Route object: RIR45.230.29.0/24Route object only in TC. Add it in the RIR database for the space.668 of 673
Route object: RIR45.230.30.0/24Route object only in TC. Add it in the RIR database for the space.668 of 673
Route object: RIR45.230.31.0/24Route object only in RADB, TC. Add it in the RIR database for the space.668 of 673

Route objects not announced

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

2804:48cc::/32ALTDB, RADB, TCNo 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.