bgpreport

Network · data from 2026-11-12

AS267135 DL CENTER PROVEDOR DE INTERNET LTDA

Registry name: AS267135 - DL CENTER PROVEDOR DE INTERNET LTDA, BR · PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS267135, 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.229.228.0/22 Valid Other IRR onlyALTDB, RADB, TC 673 100% 66
45.229.228.0/23 Valid Other IRR onlyALTDB, RADB 672 100% 66
45.229.230.0/23 Valid Other IRR onlyALTDB, RADB 672 100% 66
2804:48a4::/32 Valid Other IRR onlyALTDB, RADB, TC 633 100% 69
2804:48a4::/33 Valid Other IRR onlyRADB 633 100% 69
2804:48a4::/34 Valid Other IRR onlyALTDB 633 100% 69
2804:48a4:4000::/34 Valid Other IRR onlyALTDB 633 100% 69
2804:48a4:8000::/33 Valid Other IRR onlyALTDB 633 100% 69
2804:48a4:8000::/34 Valid Other IRR onlyALTDB 633 100% 69
2804:48a4:c000::/34 Valid Other IRR onlyALTDB 633 100% 69

AS-SET

AS267135'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 15 are in fix.csv.

  • Route object: RIR10
  • Route object: not announced5
ChangePrefix or setDetailFull-table peers
Route object: RIR45.229.228.0/22Route object only in ALTDB, RADB, TC. Add it in the RIR database for the space.673 of 673
Route object: RIR45.229.228.0/23Route object only in ALTDB, RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR45.229.230.0/23Route object only in ALTDB, RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR2804:48a4::/32Route object only in ALTDB, RADB, TC. Add it in the RIR database for the space.633 of 636
Route object: RIR2804:48a4::/33Route object only in RADB. Add it in the RIR database for the space.633 of 636
Route object: RIR2804:48a4::/34Route object only in ALTDB. Add it in the RIR database for the space.633 of 636
Route object: RIR2804:48a4:4000::/34Route object only in ALTDB. Add it in the RIR database for the space.633 of 636
Route object: RIR2804:48a4:8000::/33Route object only in ALTDB. Add it in the RIR database for the space.633 of 636
Route object: RIR2804:48a4:8000::/34Route object only in ALTDB. Add it in the RIR database for the space.633 of 636
Route object: RIR2804:48a4:c000::/34Route object only in ALTDB. Add it in the RIR database for the space.633 of 636

Route objects not announced

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

45.229.228.0/24ALTDB, RADBValid
45.229.229.0/24ALTDB, RADBValid
45.229.230.0/24ALTDBValid
45.229.231.0/24ALTDB, RADBValid
2804:1a8c::/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.