Network · data from 2026-11-12

AS269484 Start Telecom

Registry name: AS269484 - START TELECOM, BR · PeeringDB

2IPv4 routes 100.0% RPKI valid · 100.0% with a route object

3IPv6 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

1Low visibility seen by under 10% of full-table peers

5Route objects not announced registered with origin AS269484, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS269484, 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.187.40.0/22	Valid	Other IRR onlyRADB, TC	672 100%	66
2804:6558::/32	Valid	Other IRR onlyRADB, TC	634 100%	67
2804:6558::/33	Valid	Other IRR onlyRADB	345 54%	64
2804:6558:8000::/33	Valid	Other IRR onlyRADB	345 54%	64
45.187.42.0/23	Valid	Other IRR onlyRADB	1 0%low visibility	1

45.187.40.0/22

Valid

Other IRR onlyRADB, TC

672 100%

2804:6558::/32

Valid

Other IRR onlyRADB, TC

634 100%

2804:6558::/33

Valid

Other IRR onlyRADB

345 54%

2804:6558:8000::/33

Valid

Other IRR onlyRADB

345 54%

45.187.42.0/23

Valid

Other IRR onlyRADB

1 0%low visibility

AS-SET

AS269484'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: RIR5
Route object: not announced5

Change	Prefix or set	Detail	Full-table peers
Route object: RIR	45.187.40.0/22	Route object only in RADB, TC. Add it in the RIR database for the space.	672 of 673
Route object: RIR	2804:6558::/32	Route object only in RADB, TC. Add it in the RIR database for the space.	634 of 636
Route object: RIR	2804:6558::/33	Route object only in RADB. Add it in the RIR database for the space.	345 of 636
Route object: RIR	2804:6558:8000::/33	Route object only in RADB. Add it in the RIR database for the space.	345 of 636
Route object: RIR	45.187.42.0/23	Route object only in RADB. Add it in the RIR database for the space.	1 of 673

Change

Prefix or set

Detail

Full-table peers

Route object: RIR

45.187.40.0/22

Route object only in RADB, TC. Add it in the RIR database for the space.

672 of 673

Route object: RIR

2804:6558::/32

Route object only in RADB, TC. Add it in the RIR database for the space.

634 of 636

Route object: RIR

2804:6558::/33

Route object only in RADB. Add it in the RIR database for the space.

345 of 636

Route object: RIR

2804:6558:8000::/33

Route object only in RADB. Add it in the RIR database for the space.

345 of 636

Route object: RIR

45.187.42.0/23

Route object only in RADB. Add it in the RIR database for the space.

1 of 673

Route objects not announced

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


45.187.40.0/23	RADB, TC	Valid
45.187.40.0/24	RADB, TC	Valid
45.187.41.0/24	TC	Valid
45.187.42.0/24	RADB, TC	Valid
45.187.43.0/24	RADB, TC	Valid

45.187.40.0/23

RADB, TC

Valid

45.187.40.0/24

RADB, TC

Valid

45.187.41.0/24

Valid

45.187.42.0/24

RADB, TC

Valid

45.187.43.0/24

RADB, TC

Valid

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.