bgpreport

Network · data from 2026-11-12

AS267121 Atplus Telecom

Registry name: AS267121 - ATPlus Telecom, BR · PeeringDB

25IPv4 routes 64.0% RPKI valid · 88.0% with a route object
5IPv6 routes 100.0% RPKI valid · 80.0% with a route object
1RPKI invalid 1 origin · 0 maxLength
8No ROA 4 with no route object for this origin
2Low visibility seen by under 10% of full-table peers
4Route objects not announced registered with origin AS267121, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS267121, 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.

50.114.180.0/24 Invalid: origin Other origin only 3 0%low visibility 3
177.10.89.0/24 No ROA Other origin only 672 100% 67
187.84.148.0/22 No ROA Other IRR onlyRADB, TC 671 100% 66
187.84.148.0/23 No ROA Other IRR onlyRADB, TC 671 100% 66
187.84.148.0/24 No ROA Other IRR onlyRADB, TC 671 100% 66
187.84.149.0/24 No ROA Other IRR onlyRADB, TC 671 100% 66
187.84.150.0/23 No ROA Other IRR onlyRADB, TC 671 100% 66
187.84.150.0/24 No ROA Other IRR onlyRADB, TC 671 100% 66
187.84.151.0/24 No ROA Other IRR onlyRADB, TC 671 100% 66
151.247.210.0/24 Valid Nonecovered by 151.247.210.0/23 672 100% 66
2804:4870:7000::/38 Valid Nonecovered by 2804:4870::/32 1 0%low visibility 1
45.229.104.0/22 Valid Other IRR onlyRADB, TC 671 100% 66
45.229.104.0/23 Valid Other IRR onlyRADB, TC 671 100% 66
45.229.106.0/23 Valid Other IRR onlyRADB, TC 671 100% 66
151.247.211.0/24 Valid Other IRR onlyRADB 671 100% 67
45.229.105.0/24 Valid Other IRR onlyRADB, TC 670 100% 66
45.229.107.0/24 Valid Other IRR onlyRADB, TC 670 100% 66
45.229.104.0/24 Valid Other IRR onlyRADB, TC 669 99% 66
45.229.106.0/24 Valid Other IRR onlyRADB, TC 669 99% 66
2804:4870::/32 Valid Other IRR onlyRADB 632 99% 67
2804:4870:2000::/40 Valid Other IRR onlyRADB 631 99% 67
2804:4870:2f00::/40 Valid Other IRR onlyRADB 631 99% 67
2804:4870:3000::/40 Valid Other IRR onlyRADB 631 99% 67
50.114.61.0/24 Valid RIR databaseARIN, RADB 672 100% 66
104.234.1.0/24 Valid RIR databaseARIN, RADB 671 100% 66
104.234.16.0/24 Valid RIR databaseARIN, RADB 671 100% 66
104.234.41.0/24 Valid RIR databaseARIN, RADB 671 100% 66
104.234.84.0/24 Valid RIR databaseARIN, RADB 671 100% 66
104.234.90.0/24 Valid RIR databaseARIN, RADB 671 100% 66
45.147.226.0/24 Valid RIR databaseRADB, RIPE 669 99% 66

AS-SET

PeeringDB's irr_as_set for AS267121: AS-ATPLUS-ALL. 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 (AS267121 isn't in the set, or no route object for AS267121 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 objectsAS267121 in itNot covered
AS-ATPLUS-ALL TClists itself further down 2010276 Yes 2

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

  • ROA: origin1
  • ROA: none8
  • Route object: none4
  • Route object: RIR19
  • Route object: not announced4
ChangePrefix or setDetailFull-table peers
ROA: origin50.114.180.0/24ROAs covering it name AS149440, not AS267121. If AS267121 should announce it, add a ROA for AS267121.3 of 673
Route object: none50.114.180.0/24Route objects for it name AS149440. Add a route object with origin AS267121 in the RIR database for the space.3 of 673
ROA: none177.10.89.0/24No ROA covers it. Add a ROA for AS267121, maxLength 24.672 of 673
Route object: none177.10.89.0/24Route objects for it name AS263014. Add a route object with origin AS267121 in the RIR database for the space.672 of 673
ROA: none187.84.148.0/22No ROA covers it. Add a ROA for AS267121, maxLength 22.671 of 673
Route object: RIR187.84.148.0/22Route object only in RADB, TC. Add it in the RIR database for the space.671 of 673
ROA: none187.84.148.0/23No ROA covers it. Add a ROA for AS267121, maxLength 23.671 of 673
Route object: RIR187.84.148.0/23Route object only in RADB, TC. Add it in the RIR database for the space.671 of 673
ROA: none187.84.148.0/24No ROA covers it. Add a ROA for AS267121, maxLength 24.671 of 673
Route object: RIR187.84.148.0/24Route object only in RADB, TC. Add it in the RIR database for the space.671 of 673
ROA: none187.84.149.0/24No ROA covers it. Add a ROA for AS267121, maxLength 24.671 of 673
Route object: RIR187.84.149.0/24Route object only in RADB, TC. Add it in the RIR database for the space.671 of 673
ROA: none187.84.150.0/23No ROA covers it. Add a ROA for AS267121, maxLength 23.671 of 673
Route object: RIR187.84.150.0/23Route object only in RADB, TC. Add it in the RIR database for the space.671 of 673
ROA: none187.84.150.0/24No ROA covers it. Add a ROA for AS267121, maxLength 24.671 of 673
Route object: RIR187.84.150.0/24Route object only in RADB, TC. Add it in the RIR database for the space.671 of 673
ROA: none187.84.151.0/24No ROA covers it. Add a ROA for AS267121, maxLength 24.671 of 673
Route object: RIR187.84.151.0/24Route object only in RADB, TC. Add it in the RIR database for the space.671 of 673
Route object: none151.247.210.0/24No route object for it. A route object for 151.247.210.0/23 with origin AS267121 covers it (filters allowing more-specifics accept it). Add a route object with origin AS267121 in the RIR database for the space.672 of 673
Route object: none2804:4870:7000::/38No route object for it. A route object for 2804:4870::/32 with origin AS267121 covers it (filters allowing more-specifics accept it). Add a route object with origin AS267121 in the RIR database for the space.1 of 636
Route object: RIR45.229.104.0/22Route object only in RADB, TC. Add it in the RIR database for the space.671 of 673
Route object: RIR45.229.104.0/23Route object only in RADB, TC. Add it in the RIR database for the space.671 of 673
Route object: RIR45.229.106.0/23Route object only in RADB, TC. Add it in the RIR database for the space.671 of 673
Route object: RIR151.247.211.0/24Route object only in RADB. Add it in the RIR database for the space.671 of 673
Route object: RIR45.229.105.0/24Route object only in RADB, TC. Add it in the RIR database for the space.670 of 673
Route object: RIR45.229.107.0/24Route object only in RADB, TC. Add it in the RIR database for the space.670 of 673
Route object: RIR45.229.104.0/24Route object only in RADB, TC. Add it in the RIR database for the space.669 of 673
Route object: RIR45.229.106.0/24Route object only in RADB, TC. Add it in the RIR database for the space.669 of 673
Route object: RIR2804:4870::/32Route object only in RADB. Add it in the RIR database for the space.632 of 636
Route object: RIR2804:4870:2000::/40Route object only in RADB. Add it in the RIR database for the space.631 of 636
Route object: RIR2804:4870:2f00::/40Route object only in RADB. Add it in the RIR database for the space.631 of 636
Route object: RIR2804:4870:3000::/40Route object only in RADB. Add it in the RIR database for the space.631 of 636

Route objects not announced

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

151.247.210.0/23RADB, RIPEValid
2804:4870:1b0::/48RADBValid
2804:4870:1c0::/48RADBValid
2804:4870:4400::/38RADBValid

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.