bgpreport

Network · data from 2026-11-12

AS269036 ATEX

Registry name: AS269036 - DB3 SERVICOS DE TELECOMUNICACOES S.A, BR · PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS269036, 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.178.172.0/24 No ROA Other IRR onlyRADB, TC 672 100% 66
45.178.172.0/22 No ROA Other IRR onlyRADB, TC 671 100% 66
200.188.218.0/23 No ROA Other IRR onlyRADB, TC 671 100% 66
177.107.31.0/24 No ROA Other IRR onlyRADB, TC 670 100% 66
200.188.219.0/24 No ROA Other IRR onlyTC 670 100% 66
200.188.218.0/24 No ROA Other IRR onlyTC 669 99% 66
190.83.43.0/24 No ROA Other IRR onlyRADB, TC 668 99% 66
2804:5e7c::/32 No ROA Other IRR onlyRADB, TC 634 100% 67
2804:5e7c:8000::/34 No ROA Other IRR onlyTC 634 100% 67
45.178.172.0/23 No ROA Other IRR onlyRADB, TC 119 18% 41
45.178.174.0/23 No ROA Other IRR onlyTC 119 18% 41

AS-SET

PeeringDB's irr_as_set for AS269036: AS269036:AS-ATEX. Expanded from the day's IRR dumps the way bgpq4 does against whois.radb.net: a name with a database is read from that database only, one without from the first database in RADB's order. "Not covered" = this network's own routes that a filter built from the set would leave out (AS269036 isn't in the set, or no route object for AS269036 covers the route; more-specifics of a route object are accepted down to /24 and /48, as with bgpq4 -A -R 24 / -R 48). Customers' routes aren't counted: the collectors show each route's origin, not which network it came through.

NameDatabaseASNsSets Route objectsAS269036 in itNot covered
AS269036:AS-ATEX TC 6271 Yes 0

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

  • ROA: none11
  • Route object: RIR11
  • Route object: not announced8
ChangePrefix or setDetailFull-table peers
ROA: none45.178.172.0/24No ROA covers it. Add a ROA for AS269036, maxLength 24.672 of 673
Route object: RIR45.178.172.0/24Route object only in RADB, TC. Add it in the RIR database for the space.672 of 673
ROA: none45.178.172.0/22No ROA covers it. Add a ROA for AS269036, maxLength 22.671 of 673
Route object: RIR45.178.172.0/22Route object only in RADB, TC. Add it in the RIR database for the space.671 of 673
ROA: none200.188.218.0/23No ROA covers it. Add a ROA for AS269036, maxLength 23.671 of 673
Route object: RIR200.188.218.0/23Route object only in RADB, TC. Add it in the RIR database for the space.671 of 673
ROA: none177.107.31.0/24No ROA covers it. Add a ROA for AS269036, maxLength 24.670 of 673
Route object: RIR177.107.31.0/24Route object only in RADB, TC. Add it in the RIR database for the space.670 of 673
ROA: none200.188.219.0/24No ROA covers it. Add a ROA for AS269036, maxLength 24.670 of 673
Route object: RIR200.188.219.0/24Route object only in TC. Add it in the RIR database for the space.670 of 673
ROA: none200.188.218.0/24No ROA covers it. Add a ROA for AS269036, maxLength 24.669 of 673
Route object: RIR200.188.218.0/24Route object only in TC. Add it in the RIR database for the space.669 of 673
ROA: none190.83.43.0/24No ROA covers it. Add a ROA for AS269036, maxLength 24.668 of 673
Route object: RIR190.83.43.0/24Route object only in RADB, TC. Add it in the RIR database for the space.668 of 673
ROA: none2804:5e7c::/32No ROA covers it. Add a ROA for AS269036, maxLength 32.634 of 636
Route object: RIR2804:5e7c::/32Route object only in RADB, TC. Add it in the RIR database for the space.634 of 636
ROA: none2804:5e7c:8000::/34No ROA covers it. Add a ROA for AS269036, maxLength 34.634 of 636
Route object: RIR2804:5e7c:8000::/34Route object only in TC. Add it in the RIR database for the space.634 of 636
ROA: none45.178.172.0/23No ROA covers it. Add a ROA for AS269036, maxLength 23.119 of 673
Route object: RIR45.178.172.0/23Route object only in RADB, TC. Add it in the RIR database for the space.119 of 673
ROA: none45.178.174.0/23No ROA covers it. Add a ROA for AS269036, maxLength 23.119 of 673
Route object: RIR45.178.174.0/23Route object only in TC. Add it in the RIR database for the space.119 of 673

Route objects not announced

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

45.178.173.0/24TCNo ROA
45.178.174.0/24RADB, TCNo ROA
45.178.175.0/24TCNo ROA
2804:5e7c::/33TCNo ROA
2804:5e7c::/34TCNo ROA
2804:5e7c:4000::/34TCNo ROA
2804:5e7c:8000::/33TCNo ROA
2804:5e7c:c000::/34TCNo 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.