bgpreport

Network · data from 2026-11-12

AS22148 MPS Informatica

Registry name: AS22148 - MPS Informatica, BR · PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS22148, 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.
200.160.16.0/20 Valid Other origin only 671 100% 66
200.160.16.0/21 Valid None 671 100% 67
200.160.16.0/22 Valid None 671 100% 67
200.160.16.0/24 Valid None 671 100% 67
200.160.20.0/22 Valid None 671 100% 67
200.160.24.0/21 Valid None 671 100% 67
200.160.28.0/22 Valid None 671 100% 67
200.160.24.0/22 Valid None 670 100% 67
200.160.29.0/24 Valid None 1 0%low visibility 1

AS-SET

AS22148'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 10 are in fix.csv.

  • Route object: none9
  • Route object: not announced1
ChangePrefix or setDetailFull-table peers
Route object: none200.160.16.0/20Route objects for it name AS198949. Add a route object with origin AS22148 in the RIR database for the space.671 of 673
Route object: none200.160.16.0/21No route object for it. Add a route object with origin AS22148 in the RIR database for the space.671 of 673
Route object: none200.160.16.0/22No route object for it. Add a route object with origin AS22148 in the RIR database for the space.671 of 673
Route object: none200.160.16.0/24No route object for it. Add a route object with origin AS22148 in the RIR database for the space.671 of 673
Route object: none200.160.20.0/22No route object for it. Add a route object with origin AS22148 in the RIR database for the space.671 of 673
Route object: none200.160.24.0/21No route object for it. Add a route object with origin AS22148 in the RIR database for the space.671 of 673
Route object: none200.160.28.0/22No route object for it. Add a route object with origin AS22148 in the RIR database for the space.671 of 673
Route object: none200.160.24.0/22No route object for it. Add a route object with origin AS22148 in the RIR database for the space.670 of 673
Route object: none200.160.29.0/24No route object for it. Add a route object with origin AS22148 in the RIR database for the space.1 of 673

Route objects not announced

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

2804:948::/32RADBNo 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.